The official store for JNews, a WordPress theme for news, blog and magazine websites. Build a successful publishing website with JNews.
Writing & Publishing Tools
Orphan Article Finder
Find published articles with no incoming links from other bodies in a WordPress XML export. Review suspected content-link gaps and linking articles locally.
Find content-link gaps in your WordPress export
Open the XML file from WordPress Tools → Export, or paste its WXR XML. No export, post body, or URL is uploaded or requested.
Limits: 10 MiB UTF-8, 5,000 exported items, 100,000 XML elements, and 50,000 body links. Each scanned body is limited to 2 MiB and 25,000 HTML elements. Oversized inputs stop analysis without a partial report.
Normally read from the export metadata. The override establishes the original site origin and resolves relative permalinks; it does not rewrite old domains or fetch the site. Internal means the same scheme, hostname, and port.
Ready. Open a WordPress export or paste XML to begin.
Suspected orphan articles
| Article | Content-link status | Incoming sources / occurrences | Linking articles and pages |
|---|
Review suspected orphan articles before changing your site
A site-wide orphan page has no internal links leading to it. This tool only observes links saved in the included exported post and page bodies. Navigation, archives, widgets, related-post features, shortcodes, synced blocks, builder post metadata, and scripts may supply links absent from the export. A candidate here is a content-link gap to investigate, not a confirmed site-wide orphan.
How should I prepare the WordPress export?
Use Tools → Export on the original site. Include the posts and pages relevant to your review. A date-, author-, category-, or type-filtered export provides partial evidence. Drafts, private/trash/future items, password-protected content, attachments, menus, revisions, and custom post types are excluded. Export limits may require a narrower review; this tool does not join separate files or crawl missing content.
What do the counts mean?
Distinct incoming sources counts other included source records. Occurrences counts repeated links from those records. A self-link, including a jump to a heading in the same article, never rescues an orphan candidate. Published pages can contribute sources even when only posts are report targets. Unmatched internal destinations are not proven broken: they may be archives, excluded records, or URLs requiring unverified redirects.
How are URLs matched?
The browser URL parser normalizes host case, default ports, and dot segments; fragment identifiers are removed and percent-escape hex case is normalized. Path case, query parameters and order, and trailing slashes remain significant unless you opt into merging slashes. Relative body links use the exported permalink. WordPress ID aliases are matched only at the site root path, with a sole numeric p or page_id parameter and an unambiguous included record. Domains, canonical URLs, redirects, publication dates, indexability, link equity, and live destinations are not verified. Nofollow links still count as content references.
What should I do with a candidate?
Review the article on the live site, confirm it is still useful and indexable, and add contextually relevant links from appropriate guides or related articles. For older JNews archives, check generated related-post and archive links too. In Gutenverse or Gutenberg, edit the actual content block that should link to the article. This report does not automatically add links or change WordPress content.
What is exported and where is my data processed?
CSV contains filtered article metadata, counts, and linking-source record numbers. Full JSON includes all selected targets plus a compact public-source catalog to resolve those numbers. It excludes post bodies, comments, author details, passwords, and unrelated post metadata. Large source lists show the first 100 in the interface; the JSON keeps all bounded evidence. Reports are capped at 20 MiB. Everything is processed on your device, without uploads, requests to supplied URLs, storage, or a PHP processing endpoint.