NitroEcho scans your WordPress site for pages with overlapping content, flags them by severity, and shows you exactly which passages are duplicated - so you can consolidate or rewrite before Google penalises you for it.
Search engines treat duplicate content as a quality signal. When two or more pages on your site cover substantially the same material, Google has to decide which one to rank — and often ranks neither well, splitting authority across URLs instead of concentrating it. NitroEcho identifies these conflicts so you can fix them: merge pages, add canonical tags, redirect weak variants to the canonical version, or rewrite thin copy. The result is a cleaner site architecture, stronger topical authority for your target pages, and fewer indexing decisions left to chance.
NitroEcho uses a technique called MinHash locality-sensitive hashing combined with shingling. In plain terms: it breaks each page's body text into overlapping word sequences (shingles), produces a compact fingerprint (the hash), and compares fingerprints across every page pair. This is far faster than comparing full text strings and scales to large sites without excessive API cost.
Comparison runs server-side via the NitroShock worker API. Your content is sent over an encrypted connection, compared, and the results are returned — NitroShock does not store your page content beyond the time needed to process the request.
Each page pair gets a similarity score from 0–100%. NitroEcho groups results into three classes — Duplicate, Near-duplicate, and Partial overlap — based on configurable thresholds. Pairs below the partial threshold are discarded and never shown.
Go to NitroEcho → New Scan in your WordPress admin. You will see options for which post types to include (Posts, Pages, and any custom post types registered on your site) and a URL filter if you want to limit the scan to a section of your site.
Click Start Scan. NitroEcho fetches the published content for each included URL, batches the comparisons, and sends them to the worker. Progress updates appear in real time. Scan time depends on the number of pages — a 50-page site typically completes in under a minute.
Each page-to-page comparison costs one credit. A 100-page site requires roughly 4,950 comparisons (every page paired with every other page). Check your credit balance on the Settings page or at nitroshock.ai/dashboard before running large scans.
After a scan completes, go to NitroEcho → Scan Results. Results are grouped by the source page, with each matching page listed beneath it along with its similarity score, match class, and a side-by-side passage diff.
The passage diff highlights the specific sentences or paragraphs that overlap — not just the overall score. This tells you whether two pages share a boilerplate footer, a recycled introduction, or substantively identical body content. That distinction matters: a shared navigation description is usually harmless; a shared 600-word service description is a ranking problem.
Results are stored in your database until you run a new scan or clear them manually. You can revisit them at any time without using additional credits.
Duplicate (default threshold: 80% and above)
The two pages are substantially the same. Search engines are very likely treating one as a copy of the other. Immediate action recommended: redirect, consolidate, or add a canonical tag pointing to the version you want ranked.
Near-duplicate (default threshold: 50–79%)
Significant content overlap. The pages may have started from the same template or been written around the same topic without enough differentiation. Consider whether both pages need to exist, and if so, rewrite one to address a meaningfully different angle or audience.
Partial overlap (default threshold: 25–49%)
Some shared passages — commonly boilerplate sections, repeated CTAs, or shared introductory paragraphs. Usually lower priority, but worth reviewing if the shared content makes up a large proportion of a short page's body text.
There is no single right answer — the correct fix depends on why the duplication exists. Common approaches:
Redirect and consolidate. If two pages cover the same topic and one has stronger backlinks or better engagement metrics, redirect the weaker URL to the stronger one with a 301. Combine any unique content from the redirected page into the surviving one before redirecting.
Add a canonical tag. If you need both URLs to remain accessible (for example, a product available under two categories), add a rel="canonical" tag on the duplicate pointing to the preferred version. This tells search engines which URL should receive ranking credit.
Rewrite for differentiation. If both pages serve a legitimate purpose but are too similar, rewrite one to target a clearly different keyword, audience, or stage of the funnel. Thin rewrites that swap a few words won't help — the content needs to be substantively different.
No-index.. For utility pages (thank-you pages, filtered archive views, internal search results) that should never rank, add a noindex meta tag. This removes them from Google's index without deleting the URL.
Do nothing. Shared boilerplate — a footer disclaimer, a short company description that appears on several pages — typically doesn't cause problems because it makes up a small fraction of each page's content. Use your judgment based on the diff output.
Go to NitroEcho → Settings to configure the plugin.
License Key — your NitroShock license key. This is the same key used by other NitroShock plugins (NitroImg, ShockMeta, etc.) — you don't need a separate key per plugin. New accounts receive signup credits, so your first scans are typically free. Get or manage your key at nitroshock.ai/dashboard.
Balance — displays your current credit balance fetched live from the NitroShock platform. If it shows unavailable, check that your license key is saved and valid.
Test connection — sends a test request to the NitroShock worker to confirm your site can reach the API. Useful for debugging firewall or proxy issues.
The three threshold fields on the Settings page control where the boundaries between match classes fall. Values are percentages from 0–100.
The defaults (80 / 50 / 25) work well for most sites. Reasons to adjust:
Changes to thresholds take effect immediately and apply to the next scan. They do not retroactively re-classify existing results.
NitroEcho uses a pay-per-scan model billed against your NitroShock credit balance. One credit is consumed per page-pair comparison. The number of comparisons for a scan of n pages is n × (n − 1) / 2.
| Pages scanned | Comparisons |
|---|---|
| 20 | 190 |
| 50 | 1,225 |
| 100 | 4,950 |
| 200 | 19,900 |
You can reduce cost by using the post type filter or URL filter to scan only a subset of your site. For example, scanning only Pages rather than all post types will exclude blog posts, which tend to be more naturally unique.
Credits are shared across all NitroShock plugins. Top up at nitroshock.ai/dashboard.
Will NitroEcho flag my tag and category archive pages?
Only if those post types are enabled in the scan settings. WordPress archive pages are typically excluded by default because they're generated dynamically and usually noindexed anyway. If your theme generates unique archive content worth scanning, you can include custom post types explicitly.
Does it scan across multiple sites in a multisite network?
Not in the current version. Each site in a multisite network is scanned independently from its own admin. Cross-site comparison is on the roadmap.
My two pages have the same title but completely different content. Will they be flagged?
No. NitroEcho compares body text only, not titles, URLs, or metadata. Identical titles with different content won't produce a match.
How often should I run a scan?
Monthly is a reasonable default for most sites. Run a targeted scan after a content migration, a large batch of new pages, or any time you've used a page template to create multiple similar pages.
Does it work with page builders like Oxygen or Elementor?
Yes. NitroEcho reads the post content stored in the database, which is what the page builder writes to. Rendered HTML is not used, so the comparison is based on the actual written content regardless of which builder produced it.
Can I export results?
Not yet. Export to CSV is planned for a future release. For now, use your browser's print function or screenshot the results page.
