SEO-friendly Pagination with getPage - My Forums

Re: SEO-friendly Pagination with getPage

markg — Aug 09, 2018, 04:04 AM

Any updates on this?

It's been over four years since the last update and things have changed, what with infinite scrolling and mobile optimised pages to name just a few..

Be good to get an uptodate tute on this.

Then again, a modx extra that just did seo friendly pagination properly would be a great extra.

Or is that really just an update to getpage?

Beyond me, I'm not a tech guy, but happy to have the conversation.

Re: SEO-friendly Pagination with getPage

cristianb88 — Jan 21, 2015, 09:33 AM

I don't uderstand what i have this results:

I head part of page?

Re: SEO-friendly Pagination with getPage

kilroy — Sep 24, 2014, 01:33 AM

I have found an easier way to do it.

I place a snippet like this on every template that uses getpage :

';
}

else {
	echo'';
}
?>

Make sure it is uncached.

Re: SEO-friendly Pagination with getPage

esnyder — May 27, 2014, 01:00 PM

You could call getPage at the top of the template with toPlaceholder set to 1, and then insert the actual content in the right place using the placeholder.

Re: SEO-friendly Pagination with getPage

kilroy — May 21, 2014, 02:38 PM

Quote from: esnyder at May 20, 2014, 04:34 PM

Hi effect-energy, I'm not sure why that is, but now that I think about it, the best way to do what kilroy was talking about is probably to just use an output filter on the page placeholder. Put this in the :
[[!+page:is=`1`:then=``:else=``]]
That's a lot simpler than trying to figure it out inside a snippet and then return the appropriate tag.

Thank you for this solution, but for me, it only works if I put it after the getPage call.

If I put the code you provide in the , it only returns noindex, follow, even if it is on the first page.

Here is the getPage call I use in my page body:

[[!getPage@langfr?
   &elementClass=`modSnippet` &element=`getResources` &parents=`[[*id]]` &depth=`1` &limit=`2` &pageVarKey=`page` &includeTVs=`1` &processTVs=`1` &showHidden=`1` &tpl=`actualite-lien` ]]

If I put [[+page]] in the head, it returns the relevant value.

Re: SEO-friendly Pagination with getPage

esnyder — May 20, 2014, 11:34 AM

Hi effect-energy, I'm not sure why that is, but now that I think about it, the best way to do what kilroy was talking about is probably to just use an output filter on the page placeholder. Put this in the :

[[!+page:is=`1`:then=``:else=``]]

That's a lot simpler than trying to figure it out inside a snippet and then return the appropriate tag.

Re: SEO-friendly Pagination with getPage

effect-energy — May 20, 2014, 09:19 AM

...hmmm...don't know why - but in my case this is always showing the 'if' (== 1), never the 'else' (!= 1).

this:

 
  
  [[+paginated-metas]]

returns:

[[+page]]=3
[[+paginated-metas]]=1
..?

Re: SEO-friendly Pagination with getPage

esnyder — May 19, 2014, 12:57 PM

Quote from: kilroy at May 13, 2014, 08:59 AM

what method would you recommend to have ONLY on paginated pages?

I think it would be easy enough to do this with a modified version of the snippet I described in the original post. Instead of selecting unique titles and descriptions for paginated pages, the snippet would just set your meta tags the way you want them, like this:

$properties =& $scriptProperties;
$properties['page'] = (isset($_REQUEST[$properties['pageVarKey']]) && ($page = intval($_REQUEST[$properties['pageVarKey']]))) ? $page : 1;
 
if ($properties['page'] == 1) {
    $modx->setPlaceholder('paginated-metas', '');
}else{
    $modx->setPlaceholder('paginated-metas', '');
}

Then just put the placeholder [[+paginated-metas]] in your

Re: SEO-friendly Pagination with getPage

kilroy — May 13, 2014, 03:59 AM

I am also trying to implement a SEO friendly page navigation in MODx (on both Evo and Revo websites BTW).

After reading this pagination guide, there are several methods to handle it:

noindex, follow on every paginated page except the first
see all page with a canonical pointing towards it
rel="previous" and rel="next" in the page head

I have read that rel="noindex" did not work on anchor links.

So it seems to me that the first method is the one that suits my case the best.

But what method would you recommend to have ONLY on paginated pages?

Re: SEO-friendly Pagination with getPage

esnyder — Apr 14, 2013, 02:10 PM

If I understand correctly, you're saying that you want the canonical tag to point to the first page in the series of pages, but you also want to use rel="next" and rel="prev"?

My advice on that, for what it's worth, would be don't do it that way. The whole point of using the rel="next" and rel="prev" attributes is that you are telling search engines that you want them to index the next and previous pages as separate pages. But by having the canonical link element pointing to the first page, you are telling search engines that you want them to treat all of the subsequent pages as duplicates of the first page and ignore them. So that's a contradiction, and I'm not sure how search engines will interpret it.

If you're going to use rel="next" and rel="prev" you should have the canonical tag point to the actual full URL of whatever page is being displayed, as you were originally doing if I understand you correctly.

Also, there's no need to use a TV for the canonical unless you really want to for some reason - generally it's better to use this:

See this thread: http://forums.modx.com/thread/?thread=44222&i=1&page=1