Nico Knoll

MarkupSEO - The all-in-one SEO solution for ProcessWire.

Recommended Posts

On 4/17/2018 at 7:15 AM, NoremPload said:

i cannot change the length of the seo_title field. I changed the field max length to 100 but it is still 60 at the input field. i tried to remove the counter to check, does not work. Tried to change the title and description of the field, this works. I'm confused.

Check out my fork linked to above - I think this is one of the many things I fixed. If it's still an issue, feel free to submit a PR to my fork.

Share this post


Link to post
Share on other sites

First of all, this module is great!

Unfortunately I'm having some issues. Yesterday most of the SEO data was filled in for the website. We're running a multi-lingual website, so I've changed the fieldtypes and everything worked as expected except for the homepage. For example: when I am searching the company name on google (NL), the website shows up with the link to the dutch homepage which is alright, but the seo description hasn't changed while the field isn't empty in the SEO tab on the Homepage. I can see that the meta data is in the page but google doesn't use it.

1644902634_Schermafbeelding2018-05-17om10_15_43.thumb.png.de4dfd7b3eea1242070b3dfc7596bb14.png

 Is this a known issue and can it be solved or is it something different? 

Thanks in advance!

Share this post


Link to post
Share on other sites

I'm away next week, so don't expect any quick responses to this question, but I am curious if anyone is using my fork (don't forget to go to the other non-master branch)?

If you are, I'd love to hear your feedback and curious whether you think I should try to contact Nico and see if I can either take over this project, or whether I should make it a new module?

There are lots of new features and in my mind lots of pretty critical bug/functionality fixes.

Any thoughts?

Share this post


Link to post
Share on other sites

I could give it a try next week.

Never used this or the version from Nico so we will see.

Anything special I should look for?

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian

I'm not using your fork actively - because I wasn't previously aware of it. I do know people who use Nico's original module - but having had a quick look at the changes in your module I'll be switching over to using it going forward. If Nico is not currently accepting pull requests, (I know I go through phases like that with my modules) then perhaps starting an alternative module from your fork would be the way to go. MarkupSEOExtended?

  • Like 1

Share this post


Link to post
Share on other sites

Hi @netcarver - thanks for your thoughts.

Nico has just given me push permissions to the repo for this module so I could now start maintaining this module moving forward.

However, I honestly don't really want another high profile module on my list of things to support at the moment, so if I do take this on, I will be looking for the community to help with PRs moving forward. Regarding your suggestion to me via PM about a community Github organization - I still think this might be a good idea, but I am also ok with being the gatekeeper for the module, just not wanting to take on being the support person - does that make sense?

The other issue is that my fork has several breaking changes that prevent easy upgrading from the current master version that is in the modules directory, so without some manual DB changes, it should only be used for new installs.

Anyone else have any thoughts on how best to proceed to ensure no-one breaks there site when upgrading to my new version? Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

  • Like 3

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

I am yet to check out this module so I am for sure not the best person to answer this questions, however I think if you just write a short manual migration guide and prevent accidental upgrading then it should be enough for us developers.

  • Like 2

Share this post


Link to post
Share on other sites
3 hours ago, adrian said:

Anyone else have any thoughts on how best to proceed to ensure no-one breaks there site when upgrading to my new version? Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

I think your module fork should be on its own - just to minimize the risk to break a site.

I don't know if it's possible to check if Nicos version is installed and therefore your version can't get installed. Or similar.

If an upgrade() method is easy to do I'll be fine with it, too. 🙂 

 

Regarding community help... count me in as tester (at least as this). As we talk about testing, where is the best place to report issues? Github? Here?

 

Share this post


Link to post
Share on other sites

Thanks for your thoughts @wbmnfktr - not sure what I am going to do with it just yet, but if you feel like testing that branch in my fork, I think it's probably best to report issues on Github.

  • Like 2

Share this post


Link to post
Share on other sites
On 7/17/2018 at 6:28 PM, adrian said:

Hi @netcarver - thanks for your thoughts.

Anyone else have any thoughts on how best to proceed to ensure no-one breaks there site when upgrading to my new version? Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

I'd simply call it a new version with a different fork . Put a notice on the current version that a new version is available.

Perhaps a user like me can have V1 installed and then simply install separately install V2, test and then remove V1.

Share this post


Link to post
Share on other sites

I’d love to see, as an option, a user-supplied character inserted between title and sitename. For instance, I usually use the pipe (|) character or sometimes a hyphen. And this character would only obviously be inserted if both title and sitename are used. If sitename isn't supplied, then the pipe or whatever gets stripped.

  • Like 1

Share this post


Link to post
Share on other sites
On 5/17/2018 at 10:17 AM, Harmen said:

First of all, this module is great!

Unfortunately I'm having some issues. Yesterday most of the SEO data was filled in for the website. We're running a multi-lingual website, so I've changed the fieldtypes and everything worked as expected except for the homepage. For example: when I am searching the company name on google (NL), the website shows up with the link to the dutch homepage which is alright, but the seo description hasn't changed while the field isn't empty in the SEO tab on the Homepage. I can see that the meta data is in the page but google doesn't use it.

1644902634_Schermafbeelding2018-05-17om10_15_43.thumb.png.de4dfd7b3eea1242070b3dfc7596bb14.png

 Is this a known issue and can it be solved or is it something different? 

Thanks in advance!

Was this solved? Im having the same issue. Everything looks fine but the home page SEO won't update. Even if I post link through Facebook. All othes pages and suppages work fine. Looking through source all is there and looks fine. Any ideas?

Thank you

R

Share this post


Link to post
Share on other sites

Hi everyone,

I read a few things about implementing a multi-language feature of this module but I can't find anything in the module.
Has anyone managed to do a multi-language setup with SEO?

Also the meta tags are in the source file but Google doesn't use them.
Same issue as @Roych

 

Share this post


Link to post
Share on other sites

For multi-language SEO tags you can use a FieldtypeFieldsetGroup in your templates (put it on a new tab for easy access):  https://processwire.com/blog/posts/processwire-3.0.73-and-new-fieldset-types/ .. echo this vars inside an included file (or use a Markup Region) in the main template file.

PS: I never try with FieldtypeFieldsetPage, but can works too

  • Like 1

Share this post


Link to post
Share on other sites
37 minutes ago, joelplambeck said:

Hi everyone,

I read a few things about implementing a multi-language feature of this module but I can't find anything in the module.
Has anyone managed to do a multi-language setup with SEO?

Also the meta tags are in the source file but Google doesn't use them.
Same issue as @Roych

 

If you have the required language modules installed, you just change the field type of the seo fields, look for field seo_title, and see that you can change it to other types of fields, in this case, you want Text multilanguage for seo_title, it should show up after the multilanguage modules are setup. 

  • Like 2

Share this post


Link to post
Share on other sites
2 minutes ago, elabx said:

If you have the required language modules installed, you just change the field type of the seo fields, look for field seo_title, and see that you can change it to other types of fields, in this case, you want Text multilanguage for seo_title, it should show up after the multilanguage modules are setup. 

Oh wow, Thank you so much @elabx 

I could have come up with that myself. Sometimes you don't think of the easiest solution. Thanks for giving me a heads up!

You have a great day!

Share this post


Link to post
Share on other sites
2 hours ago, Peter Knight said:

Hi @adrian 

Does your fork have NoIndex and NoFollow fields by default?

Hey Peter - you can customize in the settings exactly how you want - site wide, template wide and even by page IIRC. 

However, you might want to check out: https://github.com/wanze/SeoMaestro

@Wanze looks to have done a beautiful job on this.

@GhostRider - you might also want to check that new module out.

  • Like 5

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Anssi
      A simple module to enable easy navigation between the public and the admin side of the site. After installation a green bar will appear to the upper side of the screen, containing a few navigation elements and displaying the PW version number.
      Heavily inspired by @apeisa's great AdminBar (Thanks!). I needed a bit simpler tool for my projects and as a result, this was made. Available on GitHub .

    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
    • By David Karich
      Thanks to the great Pro module "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use this module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      With this proof of concept I have created a module which adds the feature to copy a repeater item to the clipboard so that you can paste this item to another page with the same repeater field. The module has been developed very rudimentarily so far. It is currently not possible to copy nested items. There is also no check of Min/Max. You can also only copy items that have the same field on different pages. And surely you can solve all this more elegantly with AJAX. But personally I lack the deeper understanding of the repeaters. Also missing on the Javascript side are event triggers for the repeaters, which would make it easier. Like e.g. RepeaterItemInitReady or similar.
      it would be great if @ryan would implement this functionality in the core of RepeaterMatrix. I think he has better ways to implement this. Or what do you think, Ryan?
      Everybody is welcome to work on this module and improve it, if it should not be integrated into the matrix core. Therefore I put it for testing and as download on GitHub: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDublicate
      You can best see the functionality in the screencast: 
       
    • By anderson
      Hi,
      Please take a look at this:
      https://templatemag.com/demo/Good/
      The upper nav bar, including dropdowns like "pages" and "portfolios", what do you call this whole thing? At first I guess it's called "dropdown nav bar", but seems not.
      AND of course, what's the simplest way/module to achieve this in PW?
      Thanks in advance.
    • By Sebi2020
      Hey, I'm new and I created a simple module for tagging pages because I didn't found a module for it (sadly this is not a core feature). This module is licensed under the GPL3 and cames with absolutly no warranty at all. You should test the module before using it in production environments. Currently it's an alpha release. if you like the module or have ideas for improvements feel free to post a comment. Currently this fieldtype is only compatible with the Inputfield I've created to because I haven't found  an Inputfield yet, that returns arrays from a single html input.
      Greetings Sebi2020
      FieldtypeTags.zip.asc
      InputfieldTagify.zip
      InputfieldTagify.zip.asc
      FieldtypeTags.zip