WordPress 7.0 block changes can affect how template parts and navigation elements appear in block themes. Breadcrumb blocks need a separate SEO check because they influence internal links, context, and structured data.
Use this for block themes, service pages, resource hubs, WooCommerce categories, and blog archives where breadcrumbs are generated by a block, SEO plugin, or custom code.
Quick answer
WordPress 7.0 Breadcrumbs Block SEO Checklist should be handled with a narrow evidence-first workflow: map hierarchy, check canonical links, inspect schema, then verify the result before making broader changes.
What to check first
- Confirm breadcrumb labels match the real page hierarchy.
- Check whether breadcrumbs link to canonical archive or hub pages.
- Inspect structured data output for duplicate BreadcrumbList markup.
- Test mobile wrapping so breadcrumbs do not cover headings or forms.
- Compare SEO plugin output against theme block output.
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 |
|---|---|---|
| Map hierarchy | Confirm breadcrumb labels match the real page hierarchy. | Breadcrumb text and links match the intended hierarchy. |
| Check canonical links | Check whether breadcrumbs link to canonical archive or hub pages. | Only one valid BreadcrumbList appears when schema is enabled. |
| Inspect schema | Inspect structured data output for duplicate BreadcrumbList markup. | Mobile breadcrumbs wrap without covering content. |
| Test mobile output | Test mobile wrapping so breadcrumbs do not cover headings or forms. | Important hub pages receive useful internal links. |
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
curl -sS https://example.com/service-page | grep -Ei 'BreadcrumbList|breadcrumb|canonical'
wp post list --post_type=wp_template_part --fields=ID,post_title,post_modified
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.
- Map hierarchy
- Check canonical links
- Inspect schema
- Test mobile output
- Remove duplicates
Production verification checklist
- Breadcrumb text and links match the intended hierarchy.
- Only one valid BreadcrumbList appears when schema is enabled.
- Mobile breadcrumbs wrap without covering content.
- Important hub pages receive useful internal links.
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, audit WordPress breadcrumb SEO.