Skip to content
puluno

Compatibility after installation

Puluno SEO outputs its own meta tags, schema, sitemap changes, and redirects. After activation you cannot simply "add it alongside" another SEO plugin — both would do the same thing and Google would see duplicates.

Golden rule: one site = one active SEO plugin for <head> output. Puluno can import data, not run concurrently with Yoast / Rank Math.


What can collide

AreaPulunoTypical conflictSymptom
<title>pre_get_document_titleYoast, Rank Math, theme with custom titleDouble or wrong title in page source
Meta description, canonicalwp_headAnother SEO pluginTwo <meta name="description"> or two canonicals
Open Graph / Twitterwp_headYoast, Rank Math, some themesDuplicate og:title, og:image
JSON-LD schemawp_headSEO plugin + theme + WooCommerceMultiple @graph blocks, duplicate FAQPage
XML sitemapWP sitemap changesYoast /sitemap_index.xml, Rank Math sitemapTwo sitemap indexes in GSC
Redirectstemplate_redirectRank Math Redirections, Redirection pluginUnexpected redirects, loops
robots.txteditor in SettingsYoast / Rank Math robotsConflicting rules

Center and the audit assume what Puluno outputs itself — not live page HTML. If a second SEO plugin is running, Center scores may look fine, but View Source shows duplicates.


Migration from Yoast SEO

  1. Activate Puluno first — Yoast meta is automatically copied on first run (title, description, focus keyword, OG image) if Puluno fields are empty.
  2. In Settings → Import you can repeat the import manually.
  3. Verify Center — check a few URLs that meta matches.
  4. Deactivate Yoast SEO (or at least disable its head output — see below).
  5. In Search Console submit the WP sitemap (/wp-sitemap.xml) and remove the old Yoast sitemap.
  6. You can uninstall Yoast after a DB backup — meta remains in _yoast_wpseo_*, Puluno already has it in its own fields.

What Yoast import does not copy: global title templates, breadcrumbs settings, Yoast redirects (handle separately), schema types from Yoast wizard.


Migration from Rank Math

  1. Activate Puluno.
  2. Settings → Import → Rank Math meta (title, description, focus, robots noindex).
  3. Redirects → Import from Rank Math — rules from rank_math_redirections.
  4. Verify a few redirects in the browser (301/302).
  5. Deactivate Rank Math — otherwise duplicate tags and redirect module remain.

Rank Math meta is not loaded automatically like Yoast — import is a deliberate step.


Other SEO plugins (AIOSEO, SEOPress, The SEO Framework)

Puluno does not have import for all plugins. Process:

  1. Export / manually check meta on key pages.
  2. Activate Puluno + fill meta in Center or editor.
  3. Deactivate the old SEO plugin.
  4. Check source of homepage and one product / post URL.

Themes and page builders

Theme requirements

  • Template must call wp_head() in <head> (standard for quality themes).
  • Recommended add_theme_support('title-tag') — Puluno then controls title via WordPress API.
  • If the theme hardcodes <title> or meta in header.php, collision may occur — fix in child theme (remove duplicate tags).

Page builders (Divi, Elementor, …)

  • Page content — builder does not handle SEO head; theme + SEO plugin still control that.
  • Puluno detects Divi layout pages ([et_pb_ in content) and sets noindex, follow — layout templates should not be in the index.
  • Schema from builder widgets (FAQ, HowTo) may collide with Puluno Schema builder — use one schema source per page.

WooCommerce

  • Product pages: Puluno outputs Product schema when WooCommerce is active.
  • Cart, checkout, account — typically noindex (checked in audit).
  • If another plugin also outputs Product schema, disable one source.

Post-installation checklist

  1. Puluno Center → Compatibility — run scan (also runs automatically once daily and weekly)
  2. View Source on homepage — one <title>, one description meta, one canonical.
  3. JSON-LD — one main block (possibly @graph inside one <script type="application/ld+json">).
  4. GSC → Sitemaps — one active sitemap index.
  5. Redirects — test old URLs after migration.
  6. Center → Refresh audit — review orphans and noindex on important pages.
  7. llms.txt/llms.txt does not conflict with other plugins; just verify the server returns 200 for the URL.

Compatibility mode (in the plugin)

Puluno has three modes (Settings → Compatibility):

ModeBehavior
Auto (default)Disables Puluno frontend output if another SEO plugin or duplicates in live HTML are detected
Audit onlyPuluno outputs nothing on the site — only Center, import, GSC panel
Full outputAlways output (requires risk confirmation when another SEO plugin is active)

Scan checks: active SEO/redirect plugins, theme title-tag support, meta tag count on homepage (HTTP fetch), Yoast/Rank Math vs WP core sitemap conflict.

In Center you'll see the "Compatibility & SEO modules" panel with status of each output (head, schema, sitemap, redirects, robots).

If head output is disabled for compatibility, the Center audit shows tags Puluno will output when enabled — not live HTML with duplicates from another plugin.


When both plugins must run for a while

During a production transition it sometimes can't be instant. Minimum risk:

  1. Import meta into Puluno.
  2. In the old plugin disable frontend output (Yoast: SEO analysis can stay, but disable "SEO" output if the plugin allows; in Rank Math disable Meta + Sitemap + Redirections modules).
  3. Set a maintenance window and deactivate the old plugin right after.

Puluno in the admin warns if it detects active Yoast, Rank Math, or other common SEO plugins.


For agencies — what to tell the client

"We install Puluno and disable the old SEO plugin so Google doesn't get every tag twice. We transfer meta first, then uninstall the old plugin. The first week we check Search Console and a few key URLs manually."

More answers for clients: FAQ for agencies.


Technical extension (developers)

  • Filter indexscope_seo_bridge_file — load bridge PHP from child theme (custom schema, OG fallback).
  • Filters indexscope_brand, indexscope_schema_graph, indexscope_page_seo_registry — customize output without forking the plugin.
  • If the theme needs to disable part of Puluno: contact support — explicit "compatibility mode" toggles in Settings are planned for the future.
Compatibility and migration | Puluno