Meta Tags Extractor: title, description, Open Graph, hreflang avatar

Meta Tags Extractor: title, description, Open Graph, hreflang

Pricing

from $4.50 / 1,000 page checkeds

Go to Apify Store
Meta Tags Extractor: title, description, Open Graph, hreflang

Meta Tags Extractor: title, description, Open Graph, hreflang

Extracts the title, meta description, canonical, robots directives, Open Graph, Twitter card tags and hreflang of many pages at once, with length checks, preview image checks and a list of problems for each page.

Pricing

from $4.50 / 1,000 page checkeds

Rating

0.0

(0)

Developer

Ed Rayyis

Ed Rayyis

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 days ago

Last modified

Security

Limited permissions

Share

Give it a list of page URLs and it returns, for each page, the tags search engines and social sites read from the page head, with length checks and a plain list of problems.

Each page is fetched once, redirects followed, and its HTML is read as served. Scripts are not run, so tags added by JavaScript after load are not seen.

For each page you get:

  • Title and its length, marked ok, short, long or missing against your limits (default 30 to 60 characters)
  • Meta description and its length, checked the same way (default 70 to 160 characters)
  • Canonical URL, how many canonical tags the page has, and whether it points to the page itself
  • Robots: the robots meta tag, googlebot and bingbot meta tags, the X-Robots-Tag header, and indexable, false when any of them says noindex or none
  • Open Graph: every og:, article:, product: and fb: property. A property that appears more than once, such as several og:image tags, comes back as a list.
  • Twitter card: every twitter: tag
  • hreflang: every alternate link with its code and URL, plus checks for codes not in language or language-region form, the page not listing itself, no x-default, and one code pointing to two URLs
  • Preview images: with "Check preview images" on, each og:image and twitter:image (up to four per page) is requested, with its status and content type, and flagged when it does not load as an image
  • Also: the h1 headings and their count, the html lang attribute, the charset, the viewport tag, the favicon, and the schema.org types found in JSON-LD blocks, including those inside @graph

The issues list flags a page set to noindex, a missing or out of range title or description, more than one title or description, a missing canonical, two different canonicals, a canonical pointing to another URL, missing required Open Graph properties, no twitter:card, the hreflang problems above, no h1 or more than one, no viewport tag, no lang attribute, JSON-LD that is not valid JSON, and a preview image that does not load.

The Open Graph protocol names four properties as required on every page: og:title, og:type, og:image and og:url [1]. Google reads an hreflang code as an ISO 639-1 language with an optional ISO 3166-1 Alpha 2 region, asks for each language version to list itself as well as the others, and recommends x-default for unmatched languages [2].

Duplicates across the run

The key value store holds a SUMMARY record listing titles and meta descriptions used by more than one page in the run, with the pages that share each one.

Input

  • URLs (required). An address without http:// or https:// is read as https://.
  • Title and description length limits
  • Check preview images (default on)
  • Timeout per request (default 20 seconds), pages read at once (default 10), user agent

Output

Dataset: one item per URL with url, finalUrl, status, ok, title, titleCheck, description, descriptionCheck, canonical, canonicalCount, canonicalMatchesUrl, robotsMeta, botMetas, xRobotsTag, indexable, openGraph, twitter, hreflang, hreflangCheck, h1, h1Count, lang, charset, viewport, favicon, jsonLdTypes, previewImages, issues, issueCount and checkedAt. A page that answers 400 or above, is not HTML, or cannot be reached gets an item with ok false and the reason in error. Export as JSON, CSV or Excel, or read it over the API.

Pricing

Pay per event: one event per page read. Pages that fail and entries that are not valid URLs are reported and not charged.

Scope and conduct

It reads only the pages you list and their preview images. It does not log in or submit anything.

Support

Questions and problems: the Issues tab on this page. Replies are written by an AI assistant on behalf of the developer and reviewed by the developer.

References

[1] The Open Graph protocol, Basic Metadata. https://ogp.me/ [2] Google Search Central, Tell Google about localized versions of your page, sections "Supported language and region codes", "Guidelines for all methods" and "Use the x-default value for unmatched languages". https://developers.google.com/search/docs/specialty/international/localized-versions