How to Find Orphaned WordPress Pages with AI

An orphan page is usually defined as a page with no discoverable internal links, but proving that condition requires more than a crawl. Crawlers can miss pages that are not linked; WordPress can list records that are private or intentionally isolated. AI helps reconcile the evidence and classify candidates.

SEO analysis is only as reliable as the supplied evidence. A language model does not independently know crawl status, indexation, rankings, canonical selection or page performance. Treat it as an evidence organizer and hypothesis generator, then verify every finding in the appropriate source system.

In one sentence: Subtract crawled link targets from a complete eligible-URL inventory, then review navigation, sitemap and business intent before calling a page orphaned.

What this guide helps you accomplish

The output should identify public pages that appear to lack meaningful internal links, explain the evidence and propose a review path. It should distinguish true orphans from landing pages, utility pages, campaign URLs, private records and intentionally excluded content.

A useful result is not merely a polished answer. It must show which records or pages were examined, which evidence was unavailable, what the assistant inferred, what a human must decide and what actions remain prohibited.

What a successful output should contain

• Eligible URL denominator and exclusion rules.
• Inbound internal-link count and linking source pages.
• Presence in navigation, sitemap, breadcrumbs or related-content modules.
• Search and traffic evidence when supplied.
• Classification: likely orphan, weakly linked, intentionally isolated, excluded or data gap.
• Recommended next review and suitable parent or context.

Evidence and inputs to prepare

A crawl reveals links it can follow; WordPress reveals records; sitemaps reveal submitted URLs. Use them together and state which link sources the crawl included.

• Normalized URL inventory with public eligibility flags.
• Complete internal-link graph or crawl inlinks export.
• Navigation, footer, breadcrumb and related-content links.
• Sitemap membership.
• Page type, audience, owner and purpose.
• Search Console or analytics page data when available.
• Known campaign, utility and intentionally isolated URL rules.

Record the date, source, scope and known omissions for every input. Remove credentials, personal information and customer data that are not required for the task.

Define the denominator before counting orphans

Private posts, drafts, thank-you pages and temporary campaign variants may not belong in the same population as evergreen indexable content. Document inclusion and exclusion rules before calculating any count.

Weakly linked is different from orphaned

A page with one obscure footer link is technically linked but may still lack contextual support. Keep a separate class for weakly linked pages so the report does not turn a binary definition into a complete prioritization model.

A safe workflow

1. Freeze the eligible URL population and exclusions.
2. Build the internal-link graph from rendered links.
3. Join navigation, sitemap and WordPress evidence.
4. Calculate inbound links and identify zero- and low-link candidates.
5. Ask the assistant to classify purpose and intentional isolation.
6. Review high-value candidates with content and SEO owners.
7. Propose contextual source pages and anchor intent.
8. Create a separate implementation plan.
9. Re-crawl and confirm links after approval.

The workflow intentionally separates analysis from implementation. A later change stage should reference the approved output rather than quietly expanding the permissions of the analytical identity.

Prompt recipe

Before using this prompt, replace every value in square brackets. Do not paste passwords, API keys, private customer records or unrelated personal information into the instruction.

Audit the supplied WordPress URL inventory and internal-link graph for orphan candidates.

For each eligible URL, return:
- URL and WordPress ID
- Page type, status, locale and purpose
- Inbound internal-link count and source URLs
- Navigation, breadcrumb, related-module and sitemap presence
- Search or traffic evidence supplied
- Classification: likely orphan, weakly linked, intentionally isolated, excluded, or data gap
- Recommended review action
- Candidate parent or contextual source pages
- Confidence and missing evidence

Rules:
1. Use the declared eligibility rules.
2. Do not count external links as internal support.
3. Do not call a page orphaned from a crawl alone when the denominator is incomplete.
4. Do not add links or edit WordPress.
5. Preserve campaign and utility exceptions.

Why this prompt is structured this way

The schema forces the audit to expose its denominator and link evidence. The classification set avoids treating every zero-inlink URL as an error.

Recommended access boundary

Use a Read Only identity. The assistant may inspect the WordPress records included in scope, but attempts to create, edit, delete or publish content should be refused.

The workflow can affect public meaning, search interpretation, conversion or product information. Require explicit review before any change is applied.

What must remain outside this task

• No automatic link insertion.
• No removal of intentionally isolated pages.
• No claim of complete orphan detection without a complete inventory.
• No assumption that sitemap membership replaces contextual links.
• No ranking promise from adding links.

The access level is a starting recommendation, not a universal entitlement. The exact capabilities available to an identity must come from the installed product version and its published coverage.

How WP Agent Control fits

This is a general WordPress workflow, not a promise that Agent Control can edit every object or integration discussed here. For the guided path, start with public pages; plugin, theme, user, setting, file, deletion, WooCommerce, ACF and builder operations are not native guided tasks. Use separately qualified tools and permissions where required.

Get structured site information and inspect selected published pages after connecting. No temporary task is needed for this public reading. You can also browse public pages without the plugin; Agent Control adds structured access and a path toward authorized WordPress work.

Connect your AI: docs first profile · See features and compatibility: coverage

Verification checklist

• ☐ Eligibility and exclusion rules are documented.
• ☐ The denominator comes from more than the crawl.
• ☐ Inbound links identify exact source URLs.
• ☐ Intentional isolation is reviewed.
• ☐ Candidate links are contextual and relevant.
• ☐ No link or page state changed.

Common failure modes

• Crawl-only denominator: The audit cannot discover pages absent from the crawl.
• Binary thinking: Weakly linked and intentionally isolated pages are misclassified.
• Sitemap substitution: Submission is treated as equivalent to contextual internal linking.
• Random link injection: The remediation adds links from irrelevant pages just to change the count.

Advanced note

Track the internal-link graph over time and attach link-source classes. A page can then be evaluated by contextual diversity and structural role, not just raw inlink count.

Related guides

• How to Create a WordPress URL Inventory with AI
• How to Analyze WordPress Internal Links with AI
• How to Build a WordPress Internal Linking Plan with AI
• How to Inventory WordPress Content with AI

Next step

Build recommendations with the internal-link planning guide and validate the full graph with How to Analyze WordPress Internal Links with AI.