On-Page SEO Audit & Meta Tags Checker
Pricing
Pay per usage
On-Page SEO Audit & Meta Tags Checker
On-page SEO audit for any public page: check the title, meta description, canonical, robots, headings, hreflang, Open Graph and structured data. One row per page with a ready-made list of problems.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Sampon
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Features
Share
SEO Meta Tags Checker
Give this Actor a list of web pages and it reads the tags that search engines and link previews rely on: the title, meta description, canonical, robots rules, headings, hreflang, Open Graph, Twitter card and JSON-LD. Each page comes back as one row, and every row already has a plain list of what to fix, such as "Title is longer than the limit (72 characters)" or "Canonical points to a different URL".
It can also follow the internal links of a site one or two steps deep, mark titles and descriptions that several pages share, and tell you what changed since your last run.
What you put in
The only required setting is the list of pages:
{"startUrls": [{ "url": "https://www.python.org/" },{ "url": "https://www.apache.org/" }]}
To check a small site rather than single pages, add a crawl depth:
{"startUrls": [{ "url": "https://www.example.com/" }],"crawlDepth": 1,"maxPages": 200}
| Setting | What it does |
|---|---|
crawlDepth | 0 (default) checks only the listed pages. 1 also checks the pages they link to on the same site, 2 goes one step further. |
maxPages | Stops after this many pages in total (default 50). With several sites, the budget is shared between them. |
includeSubdomains | Counts blog.example.com as part of www.example.com when following links. |
compareWithPrevious | Remembers this run and marks each page as new, changed or unchanged next time. |
onlyChanges | Saves only new and changed pages. Useful for a daily or weekly schedule. |
monitorName | Runs with the same name are compared with each other. Use one name per site you watch. |
titleMinLength, titleMaxLength | Title limits in characters. Defaults 30 and 60. |
descriptionMinLength, descriptionMaxLength | Meta description limits in characters. Defaults 70 and 160. |
minWords | Below this word count a page is reported as thin (default 50). |
maxConcurrency, requestDelayMs | Speed. At most 4 pages at a time, and at least 1 second between requests to the same site by default. |
What you get
One row per page. A shortened example:
{"url": "https://www.python.org/","finalUrl": "https://www.python.org/","statusCode": 200,"redirectChain": [],"title": "Welcome to Python.org","titleLength": 21,"metaDescription": "The official home of the Python Programming Language","metaDescriptionLength": 52,"canonical": null,"canonicalIsSelf": null,"metaRobots": null,"xRobotsTag": null,"indexable": true,"h1Count": 5,"h1": ["Functions Defined", "All the Flow You'd Expect", "..."],"h2Count": 9,"hreflang": [],"openGraph": {"title": "Welcome to Python.org","description": "The official home of the Python Programming Language","image": "https://www.python.org/static/opengraph-icon-200x200.png","type": "website","url": "https://www.python.org/","siteName": "Python.org"},"twitterCard": { "card": null, "title": null, "description": null, "image": null },"structuredDataTypes": ["WebSite"],"lang": "en","viewport": "width=device-width, initial-scale=1.0","wordCount": 1029,"imagesTotal": 1,"imagesWithoutAlt": 0,"internalLinks": 126,"externalLinks": 78,"issues": ["TITLE_TOO_SHORT", "META_DESCRIPTION_TOO_SHORT", "CANONICAL_MISSING", "MULTIPLE_H1"],"issueCount": 4,"issueSummary": "Title is shorter than the minimum (21 characters); Meta description is shorter than the minimum (52 characters); No canonical link; More than one <h1> (5)","duplicateTitleUrls": [],"duplicateDescriptionUrls": [],"changeStatus": null,"checkedAt": "2026-10-10T07:48:40+00:00"}
issues holds short codes that are easy to filter on. issueSummary says the same thing in words, so you can hand the table to someone who does not know the codes.
The problems it reports:
- Status: the page fails to load, answers 4xx or 5xx, redirects, or is blocked by robots.txt
- Title: missing, too long, too short, more than one
- Meta description: missing, too long, too short, more than one
- Canonical: missing, more than one, or pointing to another URL
- Indexing:
noindexornofollowin the meta robots tag or in theX-Robots-Tagheader - Headings: no
<h1>, or more than one - Other basics: no
langon<html>, no viewport tag, images without analtattribute (an emptyalt=""is fine), noog:title, an hreflang list that leaves out the page itself, JSON-LD that is not valid JSON, very little text - Site-wide: the same title or meta description on more than one indexable page of the same site. These marks are added at the end of the run, once every page is known, and
duplicateTitleUrls/duplicateDescriptionUrlstell you which other pages share it
A short summary of the run (pages checked and how many pages have each problem) is saved as SUMMARY in the run's key-value store.
Price
Free for now. You only pay Apify's usual platform usage. In our tests the three example pages took about 5 seconds to check, and 19 pages from two sites at depth 1 took about 37 seconds, so a run of that size uses only a small fraction of a compute unit. A price per page may be added later. If that happens, it will be shown on this page before it applies to you.
How it treats the sites it reads
- It only reads the pages you list and, if you ask for it, pages of the same site linked from them.
- It reads each site's robots.txt first and follows it, including
Crawl-delay. Pages that robots.txt closes are not requested. A listed page that is closed still gets a row saying so. - By default it loads two pages at a time and waits at least one second between requests to the same site. You can make it slower, but never more than four requests at a time.
- It does not keep the text of the pages. Only counts (words, characters, links, images) and the tags themselves are saved, and e-mail addresses or phone numbers that appear in titles, descriptions or headings are replaced with
[email removed]and[phone removed].
Limits
- It reads the HTML the server sends. Tags that a site adds later with JavaScript are not seen.
- Some sites refuse automated requests or show a challenge page. Those pages come back with their status code (often 403) and are reported as errors.
- Title and description limits are counted in characters, not in pixels as search results are drawn.
- The comparison with the previous run knows only the pages that runs actually checked. A page that simply was not reached this time is not reported as removed.
- Word counts are low for languages written without spaces, such as Japanese or Chinese, so the thin content check also looks at the number of characters.
This Actor is an independent tool. It is not affiliated with Google, any search engine, or the owners of the sites it reads.