Example: Two extensions create different canonicals
An SEO plugin refers to the clean product address, while a theme extension also outputs the current URL with filter parameters. Both components can be configured individually in a plausible manner. The conflict only becomes visible in their joint HTML edition.
Finding the triggering point
Write down the conflicting values and compare an affected page to an inconspicuous page of the same type. Then, in the settings, look for functions for canonical, robots, or structured data. Check the change in a test environment by disabling only one of these output functions at a time. A blanket shutdown of all plugins conceals the actual responsibility.
Checking a limited fix
If one component already sets the correct signal, the second component should not generate it again. Document the responsible extension and the reason for the turned off function. In addition to the main page, also test pagination, variants and language versions, because plugins there often use different rules.
The fix is traceable if the previously double output is unambiguous after an empty cache and the required function is maintained. Save that configuration so that a plugin update or new theme doesn’t unnoticed the competing output.
Symptoms in the audit
- Multiple canonicals, double meta tags or changing headers
- Error only occurs with active plugin, app or extension
- Crawl result differs by cache clearance
Then they test the cause.
- 1. Separate SEO output per source
- 2. Check plugin/app order
- 3. Search source code for multiple signals
Fixed route
- Define a Source as Leading
- Deactivate double output
- Renew cache and sitemap after cleanup