AI AI Tools Guidebook
Troubleshooting

Paginated Pages Set to noindex,follow and Deep Articles Dropped

A common SEO myth says set `noindex,follow` on page 2+. Google treats long-term noindex,follow as noindex,nofollow — and your deep articles stop getting discovered.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

A blog hub like /blog/page/2/, /blog/page/3/ got the popular SEO advice: add <meta name="robots" content="noindex,follow"> so pagination doesn’t compete with the main hub but link equity still passes through. Six months later, articles linked only from page 3+ disappear from the index. Search Console shows them as “Discovered – currently not indexed” or “Crawled – currently not indexed.” The fix sounds clever but contradicts how Google actually treats long-term noindex,follow.

Google has stated publicly that pages held in noindex for an extended period are treated effectively as noindex,nofollow. Links on those pages stop passing signals. If page 2+ is the only path to articles 10 through 200, those articles become orphans.

Common causes

1. WordPress / Yoast / Rank Math pagination setting

Most SEO plugins ship with a “Noindex subpages of archives” toggle, usually on by default. It writes noindex,follow to /category/x/page/2/, /tag/y/page/3/, etc.

How to spot it: Visit yoursite.com/category/whatever/page/2/, view source, grep for robots. If you see noindex,follow, the plugin set it.

2. Astro / Next.js paginated routes with a blanket meta tag

A template like [page].astro emits <meta name="robots" content="noindex,follow"> when page > 1. The dev who wrote it read a 2014 Moz post.

How to spot it: Inspect getStaticPaths / dynamic route file. Look for any noindex branch keyed on pageNumber > 1.

3. Pagination is the ONLY internal path to deep content

Hub page links to article 1-10. Page 2 links to 11-20. Page 3 links to 21-30. No category index, no related links, no sitemap entry for articles 11+. If page 2+ is noindex, articles 11+ have zero in-links Google trusts.

How to spot it: Pick an article that lives on page 3 of your hub. Use Search Console URL Inspection → “Referring page.” If the only referrer is a noindex page, you’ve found it.

4. Sitemap omits paginated URLs and articles

Sitemap lists only the hub /blog/ and feature articles. Article URLs on page 2+ never appear. Combined with paginated pages being noindex, Googlebot has no way in.

How to spot it: Download your sitemap. Grep for one of the dropped article URLs. If absent, sitemap isn’t helping.

5. Mistaking noindex,follow for index,follow with canonical to hub

Some teams want pagination to “consolidate” with the hub via rel=canonical pointing all paginated pages back to page 1. Google ignores canonicals between non-duplicate pages. The paginated pages still get crawled, but the canonical signal is wasted and you’ve added confusion.

How to spot it: Page 2’s <link rel="canonical"> points to page 1 (different content). Search Console will report “Duplicate, Google chose different canonical” or just ignore the directive.

6. JavaScript “load more” hides the deep articles entirely

A variant: instead of paginated URLs, the hub uses a “Load More” button that fetches via JS but doesn’t push a URL. Googlebot never sees article 11+ links at all.

How to spot it: Disable JavaScript in DevTools, reload the hub. If only 10 articles appear and there’s no <a href="/blog/page/2/">, your deep articles are JS-only.

Shortest path to fix

Step 1: Decide your pagination strategy explicitly

Three valid options. Pick one:

  • A. Index all paginated pages (index,follow). Simple. Google handles duplicate hub content fine.
  • B. Canonical paginated pages to page 1 but keep index,follow. Google may still index page 2+.
  • C. Keep noindex,follow BUT add a separate sitemap of every article URL. Don’t rely on pagination as the discovery path.

Option A is safest for discovery.

Step 2: Remove the blanket noindex on page 2+

In Astro:

---
const { page } = Astro.props;
// Remove this:
// const robots = page.currentPage > 1 ? 'noindex,follow' : 'index,follow';
const robots = 'index,follow';
---
<meta name="robots" content={robots}>

In WordPress, Yoast → Search Appearance → Archives → “Show in search results: Yes.” Or Rank Math → Titles & Meta → Misc Pages → uncheck “Noindex Paginated Pages.”

Step 3: Add ALL article URLs to your sitemap

Don’t rely on crawl-through-pagination. Generate sitemap from your full article list, not from paginated HTML:

// scripts/generate-sitemap.mjs
import fs from 'node:fs';
const articles = JSON.parse(fs.readFileSync('articles.json', 'utf8'));
const urls = articles.map(a => `<url><loc>https://example.com/articles/${a.slug}/</loc></url>`);
fs.writeFileSync('public/sitemap-articles.xml', `<urlset>${urls.join('')}</urlset>`);

Step 4: Resubmit sitemap and request reindexing

Search Console → Sitemaps → resubmit. Then URL Inspection on 5-10 dropped articles → “Request indexing.”

Don’t leave any article reachable only via paginated archives. Cross-link from related articles, tag pages, “more from this author” widgets.

Step 6: Monitor in Search Console

Pages → “Discovered – currently not indexed” count should drop over 2-4 weeks as Googlebot rediscovers articles via the sitemap and new internal links.

When this is not on you

Old archived blog posts with zero external signals may never come back even after fixing pagination. That’s a content-quality / inlink problem, not a pagination directive problem.

Easy to misdiagnose as

A site speed or thin content issue. The articles themselves are fine; the problem is they became orphans because the only inbound internal link was on a noindex page Google stopped trusting as a link source.

Prevention

  • Default to index,follow on paginated archives unless you have a specific reason not to.
  • Never make pagination the only discovery path. Always also expose articles via sitemap and cross-links.
  • If you must noindex page 2+, run a quarterly orphan-page audit.
  • Avoid canonical from paginated pages to page 1 — they aren’t duplicates.
  • Don’t trust SEO advice older than ~2019 on this topic; Google’s stance shifted.

FAQ

  • Does rel=prev/next still help with pagination? No. Google deprecated support for it years ago. It’s not harmful, just ignored.
  • Should I use noindex on the very last paginated page only? No. Either all or none. Mixed signals confuse crawlers.

Tags: #SEO #Troubleshooting #Indexing #Search Console #pagination #noindex

Related Articles