Jump to content

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

Nico Knoll

Recommended Posts

HI Nico, thanks for the response. I was running 0.60, I upgraded to 0.8.2 and it seems to have fixed the issue.

Also in the google preview mode: if your URL is somewhat long will overlap on top of the Meta description. (it's a CSS issue, could always do a nowrap on the URL, or tuncate it, i'm not sure what google does.) just making you aware of the issue.

Great plugin, really liking the the ability to set character limits. Great work!


Link to comment
Share on other sites

  • 3 weeks later...
  • 5 weeks later...

Hey Nico

The solution to the preview URL wrapping over the text below for your module is this code below:

span.SEO_google_link {
  position: relative;
  overflow: hidden;
  white-space: nowrap;
  background-color: #fff;
span.SEO_google_link:after {
  content: "";
  pointer-events: none;
  position: absolute;
  width: 50px;
  height: 100%;
  top: 0;
  right: 0;
  background-image: -webkit-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: -moz-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: -ms-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: -o-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: linear-gradient(to left, #ffffff, rgba(255, 255, 255, 0));

All credit to this guy who I've been working with for a while: https://processwire.com/talk/user/2562-jw/

  • Like 1
Link to comment
Share on other sites

  • 1 month later...


at first, thanks a lot for this useful module!

I'm trying to figure out, how I can set the title for the homepage by hand, while using {title} - {sitename} automatically for all other pages. {title} - {sitename} automatically for all other pages is working fine, but the homepage shows always "Home | " before the sitename. Even though I have entered (under the homepage SEO tab) the title that I want, manually.  I prefer the sitename only for the homepage. I am sure that this can be easily solved somehow, but I don't get it :-/

Thanks for help!

Link to comment
Share on other sites

I would recommend you to turn off the SEO auto title function and do it yourself using the SEO parameters. Like this:

<title><?php echo ($page->id == '1') ? $page->seo->title : $page->seo->title.' - '.$config->seo->sitename; ?></title>
Link to comment
Share on other sites

Hey people, 

i try to chose the SmartKeywords with an tags (page | multiplearray) field.


what i have to change that i get as Keywords the title of the choosen pages ? 

currently i have the id's in the code 

<meta name="keywords" content="1088|1091|1082|1083|1084|1085|1086">

where i have to make changes in the Module  ?

	// case 'keywords': 
					 	if($configData['keywords']) {
					 		$pageData['keywords'] = $configData['keywords'];
					 	} elseif($configData['keywordsSmart'] && $page->get(implode('|', $configData['keywordsSmart'])) != '') {
					 		$pageData['keywords'] = strip_tags($page->get(implode('|', $configData['keywordsSmart'])));

or here 

// Default Keywords
		$field = $modules->get("InputfieldText");
		$field->name = "keywords";
		$field->label = __("Keywords");
		$field->description = "";
		$field->value = $data['keywords'];
		$field->columnWidth = '50%';
		$field->showIf = 'useParents=0';

		$field = $modules->get("InputfieldAsmSelect");
		$field->name = "keywordsSmart";
		$field->label = __("Smart Keywords");
		$field->description = __("We will use those fields (in this particular order) if you don't fill in the keywords field");
		foreach($fields as $selectField) $field->addOption($selectField->name);
		$field->value = $data['keywordsSmart'];
		$field->columnWidth = '50%';
		$field->showIf = 'useParents=0';

Nobody an solution for me ?? 

Edited by iNoize
Link to comment
Share on other sites

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

Can someone assist with some SEO Module questions I have?

By default, the SEO tags are outputting by default just before the </head>.

I'd like them to render instead right after the opening <head>

If I want to choose exactly where they render, someone posted that this work

 <?php echo wire('page')->seo->render; ?>

On my site, this works but renders the SEO fields twice. In the default location (before the closing HEAD) and in the preferred position after the opening HEAD.

My second question is if the following (and only) How to use is still correct?

$page->seo // includes all the default values mixed with the page related seo data

// e.g.:

// for rendering:

I might be doing this wrong but including any of the following renders nothing

echo $page->seo;


echo $page->seo->title;


Thanks - appreciate it.

Link to comment
Share on other sites


<?php echo wire('page')->seo->render; ?>



echo $page->seo->render;

are the way to go. 

In your settings you can either enable automatically insertion of the meta fields (so you dont need to do this) or you can enable "manual" and then you will need this code (or you're rendering the tags in some other way)

Link to comment
Share on other sites

In your settings you can either enable automatically insertion of the meta fields (so you dont need to do this) or you can enable "manual" and then you will need this code (or you're rendering the tags in some other way)

Ah, thanks Nico. That was it :)

Link to comment
Share on other sites


till today I used version 0.3.0.

Now I have deleted this and replaced it with 0.6.0. Since this I miss the SEO-tab.

What makes the SEO-tab apear again?


I have the same problem now after updating to Version 0.8.2.

After I have specified the templates no SEO-Tab apear again.

What can I do get my seo inputs again?

Link to comment
Share on other sites

@guenther55: Go to the settings page and select the templates that should get seo fields

I did this and now I select an other page once more, but no Seo tab!

I got the same error as @Tyssen and I am not able to deinstall the modul!

My solution for now: in site/modul directory I reactivated the 0.3.0 Version - seo tab and all inputs are back! The old version works for me and I dont see really need to update.

But I hope you can find the bug and maybe I can update with a next Version in future.

Link to comment
Share on other sites

Did just PR the german translation of this great module...;)


proud to contribute with some translation.

One Feature request comes in my mind - that would be a nice to have - and for my installations i probably would challange this with some little hooks on page saving...and some hacking - but within the moduel it would be much better.

feature of the "smart" title|description would be:

->if some smart fields are set

-> that on first page publish

-> if no SEO fields are filled out by the user

->the smart title|desc should filled in the seo_ fields

 This has the benefit that the Google Preview would work and simple editors see what really would generated at frontend -> and they can improve this output with own entries in the seo_fields....

i think this would be a hook after page save and Page::statusUnpublished.....but i'm not so expirenced to edit such a complex module...i'm just able to hack a little bit with my (german: gefährlichem Halbwissen) ;)

regards mr-fan

  • Like 1
Link to comment
Share on other sites

some little example code how i hacked the "prefilling" option into the seo_fields from own content fields....if i've the time i transform it to a simple module with some settings for the fallback fields...what this code does:

it take a look only if a user publish a page and if seo_title , desc, keywords are filled....and if not it uses several text fields that the templates provide as an fallback that the seo_ entries not empty - so you think why - The smart settings in the module do that on frontend, too!

Yes but a editor that takes a look at the SEO Tab see it empty with some strange example text....and i wanna let see him what will be the output in frontend. I don't like empty fields while in frontend some magic works that nobody see at a first glance.

This is what i meant with - fill the "smart" things in the page fields if the user doesn't set them...or i'am thinking to complicated here?

regards mr-fan

code runs in admin.php - some functions for better striptags and some other functions to get the right output....

 * 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");
						$first_content = ripTags($first_item->text);
						$default_desc = wordLimiter($first_content, 160);
				//set seo_description on publishing
				$page->set ('seo_description', $default_desc);
			// check if seo_keywords fields are exist and if they are empty
			if (!$page->seo_keywords) {
				//get the string that should be used to generate automatical keywords for this page
				//we use all textfields in the pagetable from the main content and collect them
				$keyword_texts = '';
				//is there a main content block as pagetable field pt_inhalt?
				if(count($page->pt_inhalt)>0) {
					foreach ($page->pt_inhalt as $keyword_text) {
						if ($keyword_text->title) $keyword_texts .= $keyword_text->title;
						if ($keyword_text->text) $keyword_texts .= $keyword_text->text;
						if ($keyword_text->text2) $keyword_texts .= $keyword_text->text2;
						if ($keyword_text->text3) $keyword_texts .= $keyword_text->text3;
				} else {
					$keyword_texts = $page->headline.' '.$page->kurztext.' '.$page->title;
				//rip tags
				$keyword_string = ripTags($keyword_texts);

				$default_keywords = extractKeywords($keyword_string);

				//set seo_title on publishing
				$page->set ('seo_keywords', $default_keywords);
Link to comment
Share on other sites

  • 2 weeks later...

Where I could find the echos in the module? For example if I want to change a meta tag name, maybe for example from <meta name="description" to <meta name="DC.description" ?

When I change

$field->name = "description";

in line 574 nothing happens.

I would not really change anything - regardless of it, would it be possible?

The module has no custom template, right?

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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      Link to github.com:
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • 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
      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
  • Create New...