Jump to content

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

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 post
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 post
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 post
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 post
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 post
Share on other sites
  • 3 weeks later...
  • 1 month later...

I have the Title Format option set to

{title}, {sitename}

How would I make the module use a filed called 

Long_Title instead of title but only is Long_Title is set

I tried the following using a pipe

{Long_Title | title}, {sitename}
Link to post
Share on other sites

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 post
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 post
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 post
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 post
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 post
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 post
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 post
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 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 monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.


    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
    • 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.
      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.
      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 (-).

      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.
      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.
      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.
      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.
  • Create New...