How to Check Page SEO in Your Browser (No Tools)

You can check most of a page's on-page SEO in about a minute without installing anything, using tools already in your browser. Here's the workflow: what to look at, where it lives, and where the browser stops being enough. By the end you'll be able to open any page, yours or a competitor's, and read its SEO setup on the spot.

The 60-second manual check

Three moves cover the on-page basics.

View source for the head tags. Press Ctrl+U (Windows) or Cmd+Option+U (Mac) to see the raw HTML the server sent. Use Ctrl+F inside that view and search for:

<title>: is there one, is it unique to this page, is it a sensible length?
name="description": present, specific, not duplicated from another page?
rel="canonical": does it point to this page's clean URL, or accidentally to the homepage or a staging domain?
name="robots": if you see noindex here, that's why the page isn't in Google.

That last one catches a real problem fast. A stray noindex left over from staging is one of the most common reasons a page never ranks, and it's right there in view-source.

DevTools for the rendered structure. Right-click the page and choose Inspect to open DevTools. The Elements panel shows the rendered DOM, which is what you want for anything JavaScript builds after load. In the Console, you can pull the heading outline in one line:

$$('h1, h2, h3').map(h => h.tagName + ' ' + h.innerText)

That prints every H1 through H3 in order so you can see the page's outline, spot a missing H1, or catch a heading level that skips from H1 to H3. DevTools also has a Lighthouse tab that runs a basic SEO and performance audit on demand.

Check the alt text coverage. Still in the Console:

$$('img').filter(i => !i.alt).length

That counts images with no alt attribute. Zero is the goal for content images.

View-source versus rendered: the distinction that trips people up

There are two versions of a page and they can differ. View-source (Ctrl+U) shows the HTML the server sent. DevTools Elements shows the DOM after JavaScript has run. This matters because search crawlers and social scrapers mostly read the served HTML, and if your title or meta tags are injected client-side by JavaScript, they'll be in Elements but missing from view-source, which means a scraper never sees them.

So the test is simple: if a tag shows in DevTools Elements but not in Ctrl+U view-source, treat it as invisible to crawlers until proven otherwise, and move it server-side. This one distinction explains a large share of "my meta tags aren't working" reports.

The full report without the manual work

The manual check is fast, but you're eyeballing each field. For a scored report that checks everything at once, paste the URL into the free SEO analyzer on our homepage. It pulls the title, description, canonical, robots directives, heading structure, Open Graph and Twitter tags, image alt coverage, and more in one pass, and it tells you which are missing or malformed instead of making you read raw HTML. Same checks you'd do by hand, done in one request and graded.

That's the right tool when you want a complete picture of a page, or when you're auditing a competitor and want the whole on-page setup at a glance.

One-click checks with the browser extension

If you check pages often, opening view-source and typing Console commands gets old. Our SEOtest.app Chrome extension puts the same checks one click away: open any page, click the toolbar icon, and it reads the title, meta description, canonical, headings, Open Graph tags, and indexability from the page you're on, with the character counts and warnings inline. No pasting URLs, no view-source. It reads the page you're already looking at.

The extension is the fast path for the whole workflow above. Instead of three manual moves per page, one click surfaces the same fields, which is what you want when you're reviewing a site page by page.

What a browser check cannot tell you

Be honest about the ceiling. Everything above reads the page's HTML. None of it can tell you:

Whether the page is actually indexed. View-source shows there's no noindex, but not whether Google has indexed the URL. Only Google Search Console's URL Inspection tool or a site: search confirms indexing status.
What queries the page ranks for. Browser tools see the page, not its search performance. Impressions, clicks, average position, and the queries driving them live in Search Console's Performance report and nowhere in the HTML.
Whether Google chose your canonical. You can set a canonical tag, but Google can pick a different one. Only URL Inspection tells you the "Google-selected canonical."
Crawl and coverage issues at scale. A one-page browser check won't surface that 400 URLs are excluded by robots.txt or returning soft 404s. That's Search Console's Pages report.

So the division of labor is clean: browser tools tell you how the page is built, Search Console tells you how it's performing. Use the browser for on-page setup and debugging, and check Search Console for indexing and query data. For fixing indexing problems specifically, see page not indexed in Search Console.

A repeatable order to check things in

When you want to run this fast on an unfamiliar page, do it in the same order every time so nothing gets skipped:

View-source, search noindex. If the page has a robots noindex, nothing else matters yet; that's the finding. Fix it first.
Confirm the canonical. Search rel="canonical" and read the URL it points at. A canonical aimed at the homepage or a different domain is a silent killer.
Read the title and description. Are they present, unique, and a sensible length? This is where the SEO character counter helps if a title looks long.
Check the heading outline. One H1, sensible H2s, no skipped levels. The heading analyzer does this without the Console.
Look at the Open Graph tags. If the page gets shared, confirm og:title, og:image, and twitter:card exist.

Five steps, under two minutes once it's muscle memory. The extension collapses all five into a single click, but the order is the same thing it's doing under the hood.

Frequently Asked Questions

How do I check a page's SEO in my browser?

Press Ctrl+U (or Cmd+Option+U on Mac) to view source and search for the title, description, canonical, and robots tags. Open DevTools (right-click > Inspect) to check the heading structure and run a Lighthouse audit. For a full scored report, paste the URL into an SEO analyzer instead of reading the HTML by hand.

Can I check SEO without installing anything?

Yes. View-source and DevTools are built into every browser and cover the on-page basics: title, meta tags, canonical, headings, and alt text. A browser extension or a web-based analyzer speeds it up, but nothing needs installing to do the core check.

What's the best SEO checker extension?

Look for one that reads the current page's title, meta description, canonical, headings, Open Graph tags, and indexability in one click, with character counts inline. Our SEOtest.app extension does exactly this so you don't have to open view-source on every page you review.

Why do my meta tags show in DevTools but not in view-source?

Because they're being added by JavaScript after the page loads. View-source shows the HTML the server sent; DevTools shows the DOM after scripts run. Search crawlers and social scrapers mostly read the served HTML, so client-injected tags may be invisible to them. Move those tags server-side.

Can browser tools tell me if my page is indexed by Google?

No. Browser tools read the page's HTML, not Google's index. To confirm indexing, use Google Search Console's URL Inspection tool or run a site:yourdomain.com/page search. The HTML can show there's no noindex, but only Google can confirm the page is actually in the index.

How to Check Any Page's SEO Without Leaving Your Browser