Toolkit Shelf
Find

Utility Tools

Page Links + Anchor Text Checker

Use this page links and anchor text checker to audit one published page before launch, SEO handoff, affiliate review, content QA, or redirect debugging.

Method and sources checked July 12, 2026Checks a public pageSource note included

Live checker

Page links + anchor text checker

Status
Run a guarded HTML check to inspect page links and anchor text.
Final statusNot checked

No request is sent until you run the check.

Link mixNot checked

Counts appear after parsing.

Anchor risksNot checked

Flags empty anchor text and target=_blank links without rel=noopener.

Review notes
  • Checks one public HTML URL. Local, private, reserved, non-http, and credentialed URLs are blocked.
Scope note

This checker extracts links from one fetched HTML response. It does not crawl linked pages, verify every destination status, render JavaScript, or inspect links inserted after page load.

Data freshness

No live response has been fetched yet. Run the checker to record a point-in-time source timestamp.

Web QA reports are launch checks, not crawler verdicts. Search engines, social platforms, consent flows, JavaScript rendering, and cache timing can still change what users or bots see.

Quick answer

Page Links + Anchor Text Checker: what it checks

Page Links + Anchor Text Checker fetches one public page and reports internal and external links, anchor text, duplicate destinations, rel attributes, non-HTTP links, and new-tab safety warnings. It inventories links in the fetched HTML rather than crawling every destination.

Check outputPage links and anchor text report
InputsPage URL, HTTP status, Final URL, Anchor links, Anchor text, Internal links, External links, Rel attributes
Check methodLink extraction method

Check method

Link extraction method

Link report = guarded HTML fetch + redirect follow + anchor tag extraction + href classification + anchor text and rel attribute checks

The checker fetches one public HTML URL, follows up to 5 redirects, and blocks local, private, reserved, credentialed, and non-http destinations before each request.

How to use

Steps

  1. Paste the exact public page URL you want to inspect.
  2. Run the check to fetch the final HTML response and extract anchor tags.
  3. Review internal and external link counts, empty anchor text, duplicate hrefs, rel attributes, non-http links, and new-tab warnings.
  4. Use the sample link list to spot unclear anchors, unsafe new-tab links, or destinations that need redirect checks.

Example

Sample check

Launch pageCheck whether key navigation and CTA links are present with readable anchor text
Affiliate pageReview external links and rel=sponsored or nofollow usage before publishing
Content QAFind empty anchors, duplicate hrefs, and target=_blank links missing rel=noopener

Checker use

Best for

  • Use this page links and anchor text checker to audit one published page before launch, SEO handoff, affiliate review, content QA, or redirect debugging.
  • Checking launch, migration, campaign, or support URLs before requesting indexing or handing the page to another team.
  • Capturing concrete page evidence such as redirects, headers, canonicals, robots directives, metadata, schema, headings, image alt text, or internal links.
  • Separating what the fetched HTML says from what still needs a browser crawl, Search Console inspection, platform debugger, or manual review.

Before relying on it

Check first

  • Treating one fetched URL as proof that every page, device, locale, redirect, or logged-in state behaves the same way.
  • Ignoring fetch guardrails, blocked private destinations, truncated bodies, JavaScript-rendered tags, or platform-specific preview caches.
  • Submitting or promoting a page before checking the final URL, canonical target, noindex signals, status code, and source-specific warnings together.

Details

What to know before using the output

GuardrailsPublic http/https only

Localhost, private networks, reserved IPs, credentials, and non-http redirects are blocked to avoid internal-network fetches.

Fetch scopeOne HTML response

The checker extracts links from fetched HTML. It does not render JavaScript or crawl linked pages.

Destination statusNot fetched

Use the redirect checker for individual destination status checks. This tool focuses on the source page link inventory.

Source notes

References used for this checker

MDN Web DocsDocuments the HTML anchor element, href attribute, target behavior, and rel usage.Google Search CentralDocuments link qualification values such as nofollow, sponsored, and ugc.MDN Web DocsDocuments noopener behavior for safer new-tab links.

Benchmarks

How to read the output

Anchor text: Readable.

Links with meaningful text are easier for users, assistive technology, and QA reviewers to understand.

External links: Qualified when needed.

Sponsored, user-generated, or untrusted outbound links may need rel values based on publishing policy.

New-tab links: Use noopener.

target=_blank links should include rel=noopener unless there is a deliberate reason not to.

Method and limitations

Methodology and assumptions

Check method

Link report = guarded HTML fetch + redirect follow + anchor tag extraction + href classification + anchor text and rel attribute checks

Inputs used

Page URL, HTTP status, Final URL, Anchor links, Anchor text, Internal links, External links, Rel attributes

Limitations

Web utility checkers use bounded public fetches and visible parsing rules. They do not replace a full crawl, Search Console URL inspection, authenticated testing, or platform-specific debugging tools.

Method and sources checked

July 12, 2026. The documented method, source timing, validity conditions, and reliance limits were checked on this date.

Method provenanceExternal data · toolkitshelf.page-links-static-HTML.v1
Maintained by
Toolkit Shelf
Calculation class
External data
Method version
toolkitshelf.page-links-static-HTML.v1
Primary source
User-provided public URL
Source date
At each run
Source checked
July 12, 2026
Intended audience
Site owners, developers, editors, and launch reviewers checking one public URL at a time.
Valid when
Links must appear in the fetched static HTML. Client-rendered, authenticated, blocked, or truncated links may be absent from the result.
Reliance boundary
The report inventories one page response and does not replace a rendered interaction test, full crawl, link-status audit, or editorial review of anchor meaning.
Data freshness
Each result is a point-in-time server request. Rerun the checker after the page, server, cache, or redirect behavior changes.
Cite this page

Toolkit Shelf. Page Links + Anchor Text Checker. Page version July 12, 2026. https://toolkitshelf.com/tools/page-links-anchor-checker

FAQ

Common questions

Does this crawl every linked page?

No. It extracts links from one fetched HTML response. Use the redirect checker when you need to inspect a specific destination status or redirect chain.

Does it include JavaScript-rendered links?

No. It reads the fetched HTML response only. Use a rendering crawler when links are inserted after page load.

Why does the checker block private or localhost URLs?

A public link checker must not fetch internal network targets. Blocking local, private, reserved, credentialed, and non-http destinations reduces SSRF and proxy-abuse risk.

Do utility tools upload my payload?

Use the page notes for each tool. Browser-side utilities can generate outputs locally, but the final file or code may still reveal whatever you encode or share.

Why should I test the generated output?

Scanners, printers, file viewers, apps, and platform previews can behave differently, so test the exact downloaded output before using it publicly.