Here’s what I see when I use Firefox with my user-agent set to googlebot:
<div role='navigation' itemscope itemtype='http://schema.org/SiteNavigationElement'>
<span itemprop='url'><a href="/t/show-desktop-notifications-when-available/10183?page=2" itemprop="name" rel="prev">? previous page</a></span>
<span itemprop='url'><b><a href="/t/show-desktop-notifications-when-available/10183?page=4" itemprop="name" rel="next">next page ?</a></b></span>
Hey look! We are!
Hey look! There is!
Granted, there’s not anything in
<head> about this, and there could be, that’s the single legit thing brought up in this topic… but isn’t that overkill? Shouldn’t proper
rel=prev links suffice?
I really do not want to add “PAGE X OF Y” to every
<title> tag for these pages. It’s meaningless, and far less important to the page than the actual title. So if we have a natural title of
Webmaster is giving errors of Duplicate Meta Descriptions and Duplicate Title Tags
then we “have to” add page numbers to the title because “the titles must be different” so…
Webmaster is giving errors of Duplicate Meta Descriptions and Duplicate Title Tags - PAGE 1 OF 3
As for your other concern about users editing titles and creating 5 “duplicate” titles for a topic – irrelevant. A canonical link is on every page, and it always points to the current name of the topic.
<link href="https://meta.discourse.org/t/show-desktop-notifications-when-available/10183?page=3" rel="canonical" />
So rather than bothering us about this, @mohammad, when the data was all on the page for you to look at just as I did… why don’t you ask Google why
their own Webmaster Tool doesn’t respect the proper canonical links that we put in every page?
the properly formatted, as per their own documentation,
rel=prev links on the pages, don’t allow them to detect pagination?
Because the evidence I have in front of me says we’re doing everything exactly as documented by Google. But don’t take my word for it! Feel free to take a look yourself, change your user agent to googlebot, load a longer topic, and view source yourself.