A CloudFront Function can fix host canonicalization instantly at the edge, but Search Console may keep showing the old host until Google recrawls and consolidates signals. The cleanup work is verification and monitoring.
Use this after adding a www to apex redirect, apex to www redirect, or any host-level CloudFront Function on a WordPress or headless WordPress site.
Quick answer
CloudFront Function Host Redirect Search Console Cleanup should be handled with a narrow evidence-first workflow: check old host 301, check preferred 200, clean sitemap host, then verify the result before making broader changes.
What to check first
- Fetch the old host and confirm it returns a 301 to the same path on the preferred host.
- Fetch the preferred host and confirm it returns 200 with self-canonical metadata.
- Confirm sitemap URLs use only the preferred host.
- Inspect a sample old-host URL and preferred-host URL in Search Console.
- Monitor GSC host and page rows until new impressions stop appearing on the old host.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|---|---|
| Check old host 301 | Fetch the old host and confirm it returns a 301 to the same path on the preferred host. | The old host redirects with a permanent status and same path. |
| Check preferred 200 | Fetch the preferred host and confirm it returns 200 with self-canonical metadata. | The preferred host returns a clean 200 page with self-canonical metadata. |
| Clean sitemap host | Confirm sitemap URLs use only the preferred host. | The sitemap has no old-host URLs. |
| Inspect URLs | Inspect a sample old-host URL and preferred-host URL in Search Console. | Search Console trends move toward the preferred host after recrawl. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
curl -sSI https://www.example.com/about-us
curl -sSI https://example.com/about-us
curl -sS https://example.com/sitemap.xml | grep 'www.example.com'
curl -sS https://example.com/about-us | grep -Ei 'canonical|<title>'
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Check old host 301
- Check preferred 200
- Clean sitemap host
- Inspect URLs
- Monitor GSC
Production verification checklist
- The old host redirects with a permanent status and same path.
- The preferred host returns a clean 200 page with self-canonical metadata.
- The sitemap has no old-host URLs.
- Search Console trends move toward the preferred host after recrawl.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, clean up WordPress host canonicalization.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
- WordPress www to Apex CloudFront SEO redirect check
- CloudFront prerendered HTML cache control WordPress