Jump to content

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


Nico Knoll

Recommended Posts

What kongondo wrote is right but unfortunately this doesn't work in MarkupSEO (at least I couldn't get it to work).

Fortunately it's very easy to override values because all seo fields are real fields:

$page->seo_title = $page->seo_title . ' - My custom suffix here!';

And you can do this with all the MarkupSEO fields. To set a new value for the og:image, modify the "seo_image" field (untested).

  • Like 2
Link to comment
Share on other sites

Since ->render is just another string, overriding an individual field value like ->seo_image doesn't change it. The only options appear to be (a) generating the markup myself using all of the individual field values (thus not using ->render at all), or (b) operating directly on the value of ->render, e.g. via regex.

Although (a) is the more flexible, future-proof option, at the moment I am using (b). If a future version of the module changes the markup, or I need more flexibility, I'll revisit it.

Link to comment
Share on other sites

If you set the Robots field to index and follow, can you over-ride this on an individual page?

There's a per-page Custom field in the SEO tab which reads

If you want to add other meta tags, you can do it here.

I was expecting to paste

<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

into this area but it outputs oddly as:

<meta name="META-NAMEROBOTS-CONTENTNOINDEX-NOFOLLOW" content="">

Furthermore, the original INDEX and FOLLOW still appear further up the list of META tags

Link to comment
Share on other sites

Hi there, I've discovered a bug yesterday that only seem to affect the Module in certain conditions. 

MarkupSEO seems to work ok on our site but when crawlers or SEO Profilers tries to profile our site, the module seems to encounter an error in a class construction stage and stops.

For a long time, I actually thought this was due to the Blog Module I had installed (Long story short i had lots of installation issues) and there's a particular error message that started occurring around that time in our system that I always attributed to the Blog Module Installation. 
Everything was working as far as I know, so I dismissed the errors as not something critical.

We kept getting messages from profilers/crawlers that stated they couldn't read our Meta Tags (which is produced by MarkupSEO) but when we would inspect our HTML on our servers and also on test servers, we could see all its presence. So it baffled us for a quite a while.

Then I stumbled on a SEO Profiling tool that actually showed the HTML it was using to profile, and I couldn't see any tags MarkupSEO produced.

That's when I realised there must have been an error with the Module instantiating and doing its task, when it was crawlers or profilers using the site.

So when I had a look at our error logs I realised that this reoccurring mysterious error was in fact originating from MarkupSEO.

My guess for the cause of the error is a change in how they implemented class construction in one of the different PHP versions. I'm still running on PHP 5.5 on our server and my guess is that crawlers and SEO Profilers are on a newer PHP version and there's some problems instantiating on a newer version.

This was the profiling tool I used to discover the error:

http://www.seocentro.com/tools/search-engines/metatag-analyzer.html

This is an example error log 

55 minutes ago
2015-12-21 10:14:29 guest / SQLSTATE[HY000]: General error: could not call class constructor [pageClass=Page, template=]

Happy to provide any additional info that you might need.

The site I'm working on is called sprachspielspass.de  just in case if it works on other test sites you've chosen   

  • Like 1
Link to comment
Share on other sites

Crawlers do not have any php versions only servers do (otherwise this would be a gaping security hole). So that's certainly not the problem. But you're missing head and body tags, which while technically optional in html5 are still needed by lots of crawlers.

  • Like 1
Link to comment
Share on other sites

Crawlers do not have any php versions only servers do (otherwise this would be a gaping security hole). So that's certainly not the problem. But you're missing head and body tags, which while technically optional in html5 are still needed by lots of crawlers.

You're right about the head & body tags gone AWOL.

Looks like Pro-Cache is removing them(!!) as they returned when I turned it off

I will get on the appropriate forum. 

Danke LostKobrakai

Link to comment
Share on other sites

If you set the Robots field to index and follow, can you over-ride this on an individual page?

Hi guys. Sorry for the double post just wanted to ping this again.

Basically I have Index and Follow set in the Robots part of this module.

How (via the Module)  can I set a NOFOLLOW or NOINDEX on a per-page basis to over-ride the default?

It seems like it's not possible or has been overlooked?

post-1166-0-40312200-1450713851_thumb.pn

Link to comment
Share on other sites

@peter: Good question. Haven't worked on the module for a long time now as I had a lot to do recently. Have you added this to GitHub already? I know there a couple of other open issues on Github but when I find the time to work on that module I will start with the github issues :)

Link to comment
Share on other sites

  • 4 weeks later...

I have to change some of the MarkupSEO code to adapt the right og: images from my pages...

The problem is that i use PageTableExtended to build my blocks with text, images and so on.

So i have a single "image" field and a "images" field for small galleries....so far the content building works with rendering the single pagetable parts...but

How get i the images from the single parts (like a block with text right and single image left or first image of a block of a gallery)?

I've manged to change the code from the module that i've a better fallback solution in the modul. It was no ideal solution that in the original module if you set a defaul image in the settings and actived the smartimage option....always the default image path was used...not that great deal.

i changed this lines and switched the if statements - and it works as expected:

case 'image':
	//first check for smartimages
	if($configData['imageSmart'] && count($page->get(implode('|', $configData['imageSmart']))) > 0) {
			$imageFields = $page->get(implode('|', $configData['imageSmart']));
			try {
				$pageData['image'] = $page->get(implode('|', $configData['imageSmart']))->first()->httpUrl;
			} catch (Exception $e) {
				$pageData['image'] = $page->get(implode('|', $configData['imageSmart']))->httpUrl;
			}
	//no smartimage there use default image from module settings
	} elseif($configData['image']) {
			$pageData['image'] = $configData['image'];
	}

How could i get the first image from all pagetable items of the $page?

$page->get(implode('|', $configData['imageSmart']))->first()->httpUrl;

I've no good idea right now... :undecided:

regards mr-fan

Link to comment
Share on other sites

I'm stucked again... ;)

before i waste my time on diving into the module code to get this complex thing done (get "smart" images as seo_image from pagetable templates)...i tried to setup a saveReady Hook in admin.php to test if it works...and now i have very strange output.

her is my simply (and/or stupid function):

/**
 * Hook for changing seo_* fields if empty on Page Save
 */
$pages->addHookAfter('saveReady', null, 'changeSeoFields');
function changeSeoFields(HookEvent $event) {
  $page = $event->arguments[0];
  //for this template only
  if($page->template == 'basic_page') {
  // check if seo_image exists and if it is empty
      if (!$page->seo_image) {
        //is there a main content block as pagetable field pt_inhalt?
        if(count($page->pt_contents)>0) {
          $first_i_item = $page->pt_contents->get("template=part_image|part_text_image_left|part_text_image_right|part_gallery");
            if ($first_i_item) {
              //two variation of templates with single image
              if ($first_i_item->template->name == 'part_image' || $first_i_item->template->name == 'part_text_image_left' || $first_i_item->template->name == 'part_text_image_right') {
              
                $first_i_url = $first_i_item->image->httpUrl;
              
              //or a little gallery with images  
              } elseif ($first_i_item->template->name == 'part_gallery') {
                
                $first_i_url = $first_i_item->images->first()->httpUrl;
                
              } else {
                
              $first_i_url = "";
            }
          }
        //set seo_image on publishing
        $page->set ('seo_image', $first_i_url);
        
        //messages to debug
        
        $page->message('Pfad '.$first_i_item->image->httpUrl);
        //gives me nothing image->url too

        $page->message('SeiteID '.$first_i_item);
        //gives me the id of the PT Page for example 1178        
        
        $page->message('SeiteID '.$first_i_item->name);
        //gives me the name of the PT Page for example 1178 but ->bild->name is not there, too...
      }
    }
  }
}

I get a "page with this function and this page == the pagetable item with a image ....but i can't get the image itself and the url???

I don't wanna parse the whole DOM for the first image url...since all the PW data is there but something i miss here.

regards mr-fan

Link to comment
Share on other sites

  • 2 weeks later...

Hi Nico

If you use ProCache with your module and have your module handling Google Analytics insertion, the GA code is stripped out by ProCache when you tell ProCache to minify the HTML output.

Any idea why this happens? I tweaked ProCache not to minify inline JS and it still seems to strip it out, so it's almost like your module is altering the markup and then ProCache is also altering the original markup and overriding your altered markup :)

I think it's going to be something to do with the order they run in maybe, but not sure. Thought you'd be interested anyway!

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...
  • 3 weeks later...

I have installed your module on under PW 3.0.12. Is there a way that this module grasps the summary of a page to include in the description? I'm actually using this code on the head. And, of course, OG:description should read it too.

<meta name="description" content="<?php echo $page->summary; ?>" />
Link to comment
Share on other sites

I have a hook after saveReady that change some SEO fields on publishing the page.... my editors should publish a page when the work is nearly finished so content and other things are on the line and i can with some functions create my semiautomatic SEO fields content.

Most editors don't care about SEO fields and SEO tab i have to create the content...in the example i use the summary (or in german "kurztext") that exists in article pages, if that summary is not there (like on normal pages) i cut some text from the first textfields of my pagetable contentblock templates...so you can skip this part if you just set the summary to seo_description!

So Users could overwright the seo fields but could not leave them empty... ;)

Extracted example for seo title and description ignore some own functions for formatting proposal...:

/**
 * Hook for changing seo_* fields if empty on Page Publish
 */
$pages->addHookAfter('saveReady', null, 'changeSeoFields');
function changeSeoFields(HookEvent $event) {
	$page = $event->arguments[0];
	//for this template only
	if($page->template == 'artikel'|| $page->template == 'seite') {
		// page is about to be published
		if($page->isChanged('status') && !$page->is(Page::statusUnpublished)) {
			// check if seo_title fields are exist and if they are empty
			if (!$page->seo_title) {
				//get the default value that would used as fallback
				if ($page->headline) {
					//Headline field is used for seo_title
					$default_title = ripTags($page->headline);
				} else {
					//Headline field empty - page title is used
					$default_title = ripTags($page->title);
				}
				//set seo_title on publishing
				$page->set ('seo_title', $default_title);
			}
			// check if seo_description fields are exist and if they are empty
			if (!$page->seo_description) {
				//get the default value that would used as fallback
				if ($page->kurztext) {
					$default_desc = ripTags($page->kurztext);
				} else {
					//is there a main content block as pagetable field pt_inhalt?
					if(count($page->pt_inhalt)>0) {
						//get the first text field in the pagetable and use it for the seo description
						$first_item = $page->pt_inhalt->get("template=part_text|part_text_image_left|part_text_image_right|part_text_spalten");
						$first_content = ripTags($first_item->text);
						$default_desc = wordLimiter($first_content, 160);
					}
				}
				//set seo_description on publishing
				$page->set ('seo_description', $default_desc);
			}
		}
	}
}

Best Regards mr-fan

  • Like 2
Link to comment
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 LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Description
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
       
      Best regards
      André
×
×
  • Create New...