Page-level content review
See where a guide, service, or landing page sends visitors before publication.
Analyze the internal links in one public page’s initial HTML. Review destinations, anchor text, and rel attributes, then inspect empty or generic labels before editing.
See where a guide, service, or landing page sends visitors before publication.
Confirm shared navigation and contextual links remain semantic after a component change.
Find internal destinations that still point at an old host, path convention, or redirecting URL.
The tool processes what you enter, shows a plain-language result, and gives you a safer next step. Make the change on your website, deploy it, then test the live page again.
Enter a Public page URL and select Inspect internal links. The checker fetches the page’s initial HTML and lists same-origin links in source order. Read Internal links, External links, Generic anchors, and Empty anchors together with the destination table.
Use View example to inspect the Overhyped homepage. Clear resets the URL and result. This is a read-only page check: it does not create links, edit your CMS, or fetch every destination to verify its response. Use the Broken Link Checker for destination checks.
Anchor text helps readers understand the destination. For example, a hypothetical link to /services labelled click here would be flagged as generic. A label such as Managed SEO and AEO service may be clearer when it accurately describes the destination and fits the sentence.
An empty anchor can use linked-image alt text as evidence. The checker’s simple generic-label rules are prompts for review, not a complete accessibility or editorial assessment. It reports rel attributes without deciding that every nofollow link should change.
Review empty labels, generic text, and unexpected destinations first. Same-origin means the scheme, hostname, and port match the final fetched page; another subdomain or HTTP-to-HTTPS variant may be classified as external. Fragment links can point within the current page rather than to a different document.
This check does not map the whole site, calculate click depth, find orphan pages, or suggest automatic links. For those questions, compare a broader crawl with a trusted URL inventory. After editing, deploy the source page and run the check again.
See where a guide, service, or landing page sends visitors before publication.
Confirm shared navigation and contextual links remain semantic after a component change.
Find internal destinations that still point at an old host, path convention, or redirecting URL.
Add meaningful visible text or an appropriate image alt value when the link needs an accessible name.
Replace labels such as “click here” only where a more descriptive label genuinely helps users understand the destination.
The initial HTML may differ from the rendered page. Inspect the browser accessibility tree before concluding that client-rendered links do not exist.
No. It inspects the initial HTML of one public page and reports same-origin links. Whole-site architecture and orphan-page analysis need a broader crawl or URL inventory.
It reports destinations and anchor evidence without checking every destination response. Use the related Broken Link Checker when response verification is the question.
No. It performs a read-only inspection and leaves editorial choices and publication to you.
No. Orphan-page detection needs a broader crawl or a comparison with a trusted URL inventory. This tool inspects one source page.
Yes. Relative links are resolved against the final fetched page URL before internal and external classification.
No. The tool reports rel attributes as evidence. Their intent depends on the page and should not be changed automatically.
Understand the evidence behind this tool, where its result stops, and the safer next steps to verify on a live page.
Read the guideEvidence · Limitations · Verification