One URL per line, up to 25 pages per run — the cap keeps the fetches polite to the sites being checked and the tool fair for everyone. Pages are fetched one at a time by our server.
| URL | Title | Meta description | Canonical | Robots | H1 |
|---|
Check the title, meta description, canonical and main heading of up to 25 pages in one run. Our server fetches each page; results export as CSV for your audit.
Check the title, meta description, canonical and main heading of up to 25 pages in one run. Our server fetches each page; results export as CSV for your audit.
Paste the URLs of a small site’s ten most important pages and the audit is immediate: nine carry unique titles, one product page has an empty description, and the old landing page’s canonical points at the homepage — three fixes found in under a minute, with the CSV saved as the record.
Each URL is fetched through the site’s protected fetcher — the same one the Meta Tag Analyzer uses: the address is resolved and checked first, private and internal addresses are refused, redirects are followed safely, and bodies are capped at about 1 MB. Your browser parses each returned page’s head: the title element, the meta description, the canonical link, the robots meta directive and the first H1. Fetches run sequentially with a short pause, at most 25 per run, so target sites are never hammered.
Each page is fetched from our server, so runs are kept small and sequential to stay polite to the sites being checked and fair to other tool users. Split bigger audits into batches of 25.
It shows the URL each page declares as its canonical version. Surprises here — a canonical pointing at another page, or at the homepage — are one of the most common causes of "my page will not index" problems.
The usual causes are a site blocking server fetches (403), a redirect to a login page, a timeout on a very slow host, or a non-HTML response. The error column shows the reason the fetcher reported.
The analyzer goes deep on one page, including Open Graph tags and pasted-HTML analysis. This extractor goes wide: the key fields for many pages in one comparable table.
Only public addresses can be fetched — private, loopback and internal network addresses are refused by design. Publish staging pages publicly (or use the single-page analyzer with pasted HTML) to check them.