Web Cheddar

Guide

How the WordPress page URL audit works

This tool is built for quick content QA. It reads published page data from the WordPress REST API, compares titles and URLs, and helps surface the issues most likely to slow down a launch or SEO cleanup.

What happens when you run a scan

  1. The tool normalizes the site URL you enter and builds a request to the WordPress pages endpoint.
  2. It fetches pages in batches so larger sites can still be reviewed in one session.
  3. Each result is checked for missing titles, off-domain links, duplicate slugs, duplicate URLs, and slug mismatches.
  4. The results can be filtered, copied, and exported for handoff to a developer, content editor, or SEO specialist.

The audit is read-only. It does not edit pages, change permalinks, or touch your WordPress admin.

Before you run a scan

  • Confirm the site is reachable and the WordPress REST API is enabled.
  • Use the production or canonical domain when possible so host checks are meaningful.
  • Run one full scan first, then use filters to focus only on flagged pages.
  • If needed, export CSV for editorial teams and JSON for development follow-up.

For staging environments, make sure any basic auth, firewalls, or security plugins allow API responses to pass through.

How to prioritize fixes

  1. Start with off-domain URLs to prevent traffic leakage and migration errors.
  2. Fix missing titles next so teams can quickly identify pages in exports and reports.
  3. Review duplicate slugs and duplicate URLs to reduce indexing confusion.
  4. Treat slug mismatches as cleanup work unless they reflect intentional permalink structure.

This order usually gives the fastest improvement in scan quality after each content update.

Troubleshooting

What to check if loading fails

WordPress API unavailable

Check that the target site serves /wp-json/wp/v2/pages. Some hosts or security plugins block API access by default.

403 or 401 responses

This usually means access restrictions are active. Verify caching, WAF, bot protection, or login requirements on staging domains.

Timeouts

Large sites or slow hosts can time out. Run again, reduce server load, or test from a network with fewer restrictions.

When this audit is most useful

Site migrations

Use it after moving a site to a new domain or subdomain to catch URLs that still point to the old location.

SEO reviews

Run it when checking slug consistency, duplicate content risk, and page title completeness across a content set.

Pre-launch QA

Scan right before launch to confirm that page URLs and labels still line up after content edits, redirects, or template changes.

Ongoing maintenance

Use scheduled spot checks after plugin updates, permalink changes, or bulk page imports to catch regressions early.

Recommended workflow

Simple handoff process for teams

  1. Run a baseline scan and record total flagged pages.
  2. Export CSV for content edits and JSON for technical remediation.
  3. Fix issues in priority order: off-domain, missing titles, duplicates, then slug mismatches.
  4. Re-scan and compare flagged counts to confirm that fixes were applied correctly.

This repeatable loop works well for agencies, internal marketing teams, and migration projects where multiple people need clear audit output.