Wanze

SeoMaestro

Recommended Posts

A module helping you to manage SEO related tasks like a boss!

  • Automatically generates and maintains a XML sitemap from your pages.
  • Includes a Fieldtype and Inputfield to manage sitemap settings and meta data for pages (title, description, opengraph, twitter etc.)
  • Multi language support for the sitemap and meta data.
  • Configure default values for meta data on template level and let pages inherit or overwrite them individually.
  • Map existing fields to meta data, reducing the need to duplicate content.

Check out the README on GitHub for more details, including usage instructions. The module is currently released as alpha and needs testing! Please report any issues on GitHub or in this forum thread, if you find time to give it a try ūüôā

Cheers

seomaestro_inputfield.thumb.png.15a669b43c45918e06067bf87018ca85.png seomaestro_inputfield_config.thumb.png.03087bb6c358e8fa4e547b7a9b4211d8.png

  • Like 24
  • Thanks 3

Share this post


Link to post
Share on other sites

This module looks AWESOME, @Wanze !! Thank you, thank you, thank you!  I'll test it on a new project ASAP to give feedback.

  • Like 1

Share this post


Link to post
Share on other sites

Just noticed that the module does not work correctly on single language installations, as I always tested on multi language setups. Should be easy to fix though, I know what the problem is¬†ūüėĄ¬†Cannot fix it today, so if you are testing, you might want to test with multiple languages. Sorry for this, I obviously should have tested this myself.¬†Cheers!

  • Like 1

Share this post


Link to post
Share on other sites

So it is multilanguage-first.

Share this post


Link to post
Share on other sites

Wow. Thank you for this great module. Hope I can test and use it soon.

Share this post


Link to post
Share on other sites

Very cool! I used this other markup-seo module since yet but I think I will try to switch soon, because I had to trick some stuff into the other module to get multilang.

One thing what would be cool, I guess: the whole SEO-Fields into an extra "SEO" tab on the page.

Share this post


Link to post
Share on other sites

Version 0.3.0 should fix problems on single language installations.¬†ūüėÖ¬†I will update Travis CI to run the test suite on two installation profiles (single and multi language).

5 hours ago, tiefenbacher_bluetomato said:

One thing what would be cool, I guess: the whÔĽŅole SEO-Fields into an extra "SEO" tab on the page.

This is possible, just wrap the Seo Maestro field in an InputFieldsetOpen.

  • Like 3

Share this post


Link to post
Share on other sites

Great work Wanze!  

15 hours ago, tiefenbacher_bluetomato said:

One thing what would be cool, I guess: the whole SEO-Fields into an extra "SEO" tab on the page.

I think this functionality will be useful and a real time saver for most of the users. 

The easiest way to achieve this, is by allowing the user to select the templates that requires the SEO tab. Like in the Markup SEO plugin

a8FrN

 

Share this post


Link to post
Share on other sites
22 hours ago, B3ta said:

Great work Wanze!  

I think this functionality will be useful and a real time saver for most of the users. 

ÔĽŅÔĽŅ The easiest way to achieve this, is¬†by allowing the user to select¬†the templates that requires the SEO tab. Like in the¬†Markup SEO¬†plugin

 

Thanks @B3ta

I think that the decision where the Seo Maestro field is rendered should be left to the user. And it should be done in the same way it works for all fields: By editing the template and placing the field. Display it in a new tab? Create an InputfieldFieldsetOpen and wrap the field. But maybe the content editor only needs to see meta title and description - then it's not worth to create a new tab.

I understand that it requires some manual work to add the field to all templates, but I don't think it is the responsibility of the module to do this. There are other solutions like the Migrations module, which can do this task in a few milliseconds. For the project I built this module, it took me 10 minutes to write a migration that creates and configures the field, adds it to all templates, tweaks the settings per template and also wraps it in a tab. No need to do this by hand if I deploy to production.

Cheers

  • Like 6

Share this post


Link to post
Share on other sites
9 minutes ago, Wanze said:

Thanks @B3ta

I think that the decision where the Seo Maestro field is rendered should be left to the user. And it should be done in the same way it works for all fields: By editing the template and placing the field. Display it in a new tab? Create an InputfieldFieldsetOpen and wrap the field. But maybe the content editor only needs to see meta title and description - then it's not worth to create a new tab.

I understand that it requires some manual work to add the field to all templates, but I don't think it is the responsibility of the module to do this. There are other solutions like the Migrations module, which can do this task in a few milliseconds. For the project I built this module, it took me 10 minutes to write a migration that creates and configures the field, adds it to all templates, tweaks the settings per template and also wraps it in a tab. No need to do this by hand if I deploy to production.

Cheers

I think this is okay - maybe to put some documentation note about that in the readme for user's who used MarkupSEO and will migrate zu SeoMaestro.

  • Like 1

Share this post


Link to post
Share on other sites

hi Guys

I try again with Processwire and now I finally want to improve my PHP knowledge.

I just joined the SEO-Maestro like this one.

  <?php
    $page->seo->render();
  ?>


Nu I get but this message.

Quote

Fatal error: Uncaught Error: Call to a member function render() on null in /var/www/vhosts/hosting115194/httpdocs/www.example.de/site/templates/_main.php:22 Stack trace: #0 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/TemplateFile.php(297): require() #1 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/Wire.php(380): ProcessWire\TemplateFile->___render() #2 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___render', Array) #3 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array) #4 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/modules/PageRender.module(514): ProcessWire\Wire->__call('render', Array) #5 /var/www/vhosts/hosting115 in /var/www/vhosts/hosting115194/httpdocs/www.example.de/site/templates/_main.php on line 22

Schwerwiegender Fehler: Uncaught Error: Call to a member function render() on null in /var/www/vhosts/hosting115194/httpdocs/www.example.de/site/templates/_main.php:22
Stack trace:
#0 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/TemplateFile.php(297): require()
#1 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/Wire.php(380): ProcessWire\TemplateFile->___render()
#2 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___render', Array)
#3 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array)
#4 /var/www/vhosts/hosting115194/httpdocs/www.example.de/wire/modules/PageRender.module(514): ProcessWire\Wire->__call('render', Array)
#5 /var/www/vhosts/hosting115 (Zeile 22 in /var/www/vhosts/hosting115194/httpdocs/www.example.de/site/templates/_main.php)

Diese Fehlermeldung wurde angezeigt wegen: Site ist im Debug-Modus. ($config->debug = true; => /site/config.php). Fehler wurde protokolliert

 

Share this post


Link to post
Share on other sites

@csaeum Are you sure that the name of your Seo Maestro field is "seo"? Did you create the field? Looks like the $page is not aware of it.

Cheers

Share this post


Link to post
Share on other sites

Thank you for your answer.

I did not think so far. In order to get used to it, I did not call it seo but seo_Maestro

thank you for your quick help

Share this post


Link to post
Share on other sites
On 2/8/2019 at 4:32 PM, Wanze said:

I understand that it requires some manual work to add the field to all templates

With the the relatively new ProField FieldtypeFieldsetGroup it should be a quick job to add this to all templates.

  • Like 2

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.