Search Atlas Help Center

⚠️ OTTO and Paginated Archive Pages Limitation

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

When you deploy OTTO across your WordPress site, you may notice that canonical tags are not applied to paginated archive pages such as /blog/2/, /blog/3/, or similar numbered URL paths. This is intentional behavior, not a deployment failure. This article explains why OTTO skips these pages and what your options are.

📄 What Are Paginated Archive Pages?

Paginated archive pages are automatically generated by WordPress when your blog or post archive spans multiple pages. They follow a pattern like:

  • /blog/ — the root archive page (page 1)
  • /blog/2/ — page 2 of the archive
  • /blog/3/ — page 3 of the archive

These pages are distinct from individual posts, category pages, or static pages, and they are handled differently by OTTO during deployment.

⚙️ Why OTTO Skips These Pages

OTTO intentionally excludes paginated archive pages from canonical tag deployment to prevent a known conflict with Divi's pagination JavaScript. Here is what happens when OTTO attempts to inject canonical tags on these pages:

  1. OTTO inserts its canonical tag module into the page's module sequence in the WordPress head.
  2. This insertion shifts the numbering of existing modules on the page.
  3. Divi's pagination JavaScript relies on fixed module numbers to function correctly.
  4. The numbering shift causes Divi's pagination to break, resulting in non-functional page navigation for site visitors.

To protect your site's user experience and prevent pagination from breaking, OTTO skips canonical tag injection on all paginated archive pages. This limitation is tracked internally as WP-315.

✅ What OTTO Does Cover

OTTO successfully deploys canonical tags on all other supported page types, including:

  • Individual blog posts and pages
  • The root archive page (/blog/ or equivalent)
  • Category and tag archive pages (non-paginated)
  • Product pages and other custom post types
  • Homepage and static landing pages

🛠️ How to Manage Canonicals on Paginated Archive Pages

Because OTTO does not write canonical tags to paginated archive pages, you have two recommended options for handling these URLs:

  • Use your SEO plugin directly: If you are running Yoast SEO, Rank Math, or another SEO plugin, you can configure canonical tag behavior for paginated archives from within that plugin's settings. Most plugins handle paginated archive canonicals automatically by default.
  • Leave the default browser canonical: WordPress and most themes output a default canonical tag for paginated archive pages that points back to the correct URL. If you have not customized these pages, the default behavior is typically acceptable for SEO purposes.

You do not need to take any action to fix a deployment error. OTTO has not failed on these pages — it has skipped them on purpose.

🔎 How to Confirm This Is the Expected Behavior

To verify that OTTO's skipping behavior is the cause and not an unrelated issue, follow these steps:

  1. Go to OTTO SEO in the left sidebar of your Search Atlas dashboard.
  2. Open your connected site and navigate to the OTTO deployment report for your site.
  3. Search for the paginated archive URL (for example, /blog/2/).
  4. If the URL appears with a skipped or not applicable status rather than a failure status, OTTO has correctly identified and excluded it per this limitation.

If the URL shows an unexpected error status unrelated to skipping, that may indicate a separate issue worth investigating.

❓ Frequently Asked Questions

Will this limitation affect my SEO? In most cases, no. Paginated archive pages carry relatively low individual SEO value. Search engines generally handle paginated archives well when standard WordPress or plugin-generated canonical tags are in place.

Does this apply to all themes, or only Divi? The confirmed conflict is specific to Divi and its pagination JavaScript. However, OTTO applies this skip rule to all paginated archive pages as a precautionary measure to avoid similar conflicts with other themes that use module-dependent JavaScript.

Will OTTO ever support paginated archive pages? This is a known limitation tracked under WP-315. Our engineering team is aware of it and is evaluating solutions. We will update this article when support is added.

💬 Need More Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.