GoDesign Technologies

Free checker · SEO and Visibility

Meta Tag and Open Graph Checker.

Fetches a live URL and shows every tag in its head, with a Google result preview at the width Google actually truncates at and a plain reading of what each tag does. Covers indexability, the social share card and the favicon.

Runs entirely in your browserNo signup, no email wallReviewed

The page is fetched once, read, and thrown away. Nothing about the address you enter is stored.

Check done

Want someone to fix what this found?

Finding a problem and fixing it are different jobs, and the second one is ours. Send the result over and you get back what it would take to put right — scoped and priced, from the person who would do the work, within one business day.

What this tool measures

This fetches a page once, with nothing executed, and reads what is in its head. Title, description, canonical, robots directives, the Open Graph and Twitter tags a share preview is built from, the language attribute, the viewport tag and the favicon link. It reports what each one says and, where it matters, what the consequence is.

The reason these are one tool rather than five is that they fail together. A page with a perfect title and a noindex directive is invisible. A page with a good description and no og:image shares as a grey box. Checking them separately is how you pass three tools and still do not appear anywhere.

How to use it

Enter any page, not just a home page. Meta tags are per-page, and the pages that are wrong are almost never the home page — somebody looked at that one. It is the template-generated pages, the ones nobody has opened since launch, where the title is still “Untitled” or every page shares one description.

Check a competitor's page too. The tags are public, so this is a legitimate way to see how a page that outranks you is described, and whether the difference is the writing rather than anything technical.

How to read the result

Start at the top of the findings list, because it is ordered by consequence rather than by where the tag sits in the document. A noindex directive appears first for a reason: while it is there, nothing else on the list changes anything.

The preview above the findings is drawn at the pixel widths Google truncates at, not at a character count. That difference is not pedantry — a title of sixty narrow characters fits and a title of fifty-five wide ones does not, and the character count everybody quotes cannot tell them apart.

Treat the preview as the version shown when your description is the best answer to the query. Google rewrites descriptions on the majority of results to match what was actually searched for, and rewrites titles on a meaningful minority. Yours is most likely to survive on branded searches, which is exactly where it matters most.

What to do next

Fix anything marked as a failure first, then come back to the warnings. A missing viewport tag or a noindex is a different class of problem from a description that could be better written.

If several pages share a description, that is a template problem rather than a copywriting one. Find where the template writes the head and give it a per-page value; writing thirty descriptions by hand into a system that ignores them is a wasted afternoon.

Questions people ask

Google shows a different title from the one I set. Why?

Google rewrites titles when it judges yours a poor match for the query, when it is stuffed with keywords, when it repeats the brand name, or when the H1 on the page describes the content better. The fix is almost always to make the title an accurate, specific description of the page rather than to fight the rewrite.

Does the meta description affect rankings?

No, and it has not for a very long time. It affects whether someone clicks, which affects everything downstream of that. Both statements are true at once, which is why the advice to ignore it entirely is as wrong as treating it as a ranking factor.

Why does it say my page has no content when I can clearly see it?

Because the fetch runs no JavaScript. If the tags are added client-side by a script or a tag manager, they are not in the response and this tool will not see them — and nor will most crawlers on the first pass. That is the finding, not a limitation.

What size should the og:image be?

1200 by 630 pixels, under about 5 MB, served over https at an absolute URL. That one image covers Facebook, LinkedIn, WhatsApp, Slack and X. A relative path is the most common reason a share preview is blank.

Where to go from here

Built by GoDesign FZE, who run technical SEO fixes for UAE sites.

Get in touch

Want someone to just do this part?

The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.

  • You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
  • A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
  • One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
scale@godesign.ae+971 58 903 1983, WhatsApp enabled

Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan

One reply from the person who would do the work, within one business day. Your details stay with GoDesign FZE and are never sold or passed on.

Would rather type than fill in a form?

Message on WhatsApp