Audit any page in seconds, yours or a competitor's.

What the SEO Analyzer is for

The Rilea SEO panel in the post editor checks your content as you write: your keyphrase, your readability, your links. But some of what matters for SEO isn't in the content at all. It's in the finished page that browsers and search engines receive: the title tag your theme actually prints, whether there's one H1 or three, whether the canonical points where it should, whether the structured data made it onto the page, and how heavy the page is.

The SEO Analyzer looks at that finished page. You give it a URL, it fetches the page exactly as a visitor's browser would, and it runs 24 checks on what comes back. Because it works from the live page, it catches problems that only show up after your theme, other plugins and your cache have had their say.

The 24 checks

Response and security

• HTTP status. The page should return 200. Anything else, such as a redirect or an error, is flagged.
• Response time. Under 1.5 seconds is good; over 3 seconds is a problem.
• HTTPS. Whether the page is served securely.
• HTML size. Very large pages take longer to download and process.
• Compression. Whether the server compressed the page with gzip or Brotli.

Search result appearance

• Title tag. Present, with its text and length. Roughly 30 to 60 characters is the target range.
• Meta description. Present, with its text and length. Roughly 120 to 160 characters is the target range.

Structure and content

• H1 heading. Exactly one is best. None is a problem; several is worth a look.
• H2 subheadings. How many there are, since subheadings help both readers and search engines.
• Word count. Pages under 300 words are flagged as possibly thin.
• Image alt text. How many images there are and how many lack alt text.
• Links. The number of internal and external links.

Indexing

• Canonical. Whether a canonical tag is present, and where it points.
• Indexable. Whether a robots meta tag blocks indexing.
• HTML lang. Whether the page declares its language.
• robots.txt. Whether the site has one.
• Sitemap referenced in robots.txt. Whether search engines can find the sitemap from it.

Mobile, sharing and schema

• Mobile viewport. The tag that makes pages display properly on phones.
• Open Graph tags. Four or more is good; none means shares on social networks may look broken.
• X card. Whether X card tags are present.
• Structured data. Which schema types were found in the page's JSON-LD.
• Favicon. Whether the page links a site icon, which search results and browser tabs use.

Page weight

• Asset requests. The number of script and stylesheet files the page loads.
• Inline styles. How many elements carry their own inline style, a sign of heavy page builder output.

Each check is marked as good, worth a look or a problem, and shows what was found, such as the actual title text or the schema types detected.

Auditing your own pages

Start with the pages that matter most: your homepage, your top landing pages, a typical blog post and, for a store, a typical product and category page. Common findings include:

• Two H1 headings, often because the theme prints the site name as an H1 as well as the page title.
• A missing or duplicated meta description on pages created before an SEO plugin was installed.
• No structured data, which can mean another plugin is removing it or a caching layer is serving an old copy.
• Images without alt text added by a theme or page builder.
• Dozens of script and stylesheet files, often from plugins that load their assets on every page.

After fixing something, run the analyzer again to confirm. If the result doesn't change, clear your cache: the analyzer sees what visitors see, including cached pages.

Analysing competitors

The analyzer works on any public URL, so you can look at pages that rank above yours. It won't tell you why a page ranks, because rankings depend on much more than on-page factors. But it shows you how a competitor has set up the basics: how long their title is and how they phrase it, how much content the page has, how they use headings, which schema types they include, and how heavy the page is.

Compare the results side by side with your own page for the same search. Differences in structured data, content depth or headings are often good starting points for improving your page. Be respectful: analyse individual pages when you need to, rather than running large numbers of requests against another site.

How it fits with the rest of Rilea SEO

• Content analysis in the editor checks your writing against your keyphrase and for readability, before you publish.
• The SEO Analyzer checks the finished page after it's published, including what your theme and other plugins add.
• Link Insights looks across your site for orphaned content and link counts.
• The dashboard summarises scores, redirects and 404s across the site.

Used together, they cover the writing, the page and the site.

Limits worth knowing

• One page at a time. It's an on-page audit, not a crawler. It won't find broken links across your whole site.
• Server-side fetch. The page is fetched from your web server, without running JavaScript. Content that appears only after scripts run may not be counted.
• Response time is approximate. It's measured from your server, so it reflects network conditions as well as the page itself. Use dedicated tools such as PageSpeed Insights for detailed performance work.
• Some sites block automated requests. If a site refuses the request, the analyzer shows the error it received.

Who can use it

The SEO Analyzer is available to administrators and to any role you give Rilea SEO's bulk editing and tools permission in the role manager. By default, that includes editors. The fetch uses WordPress's safe request functions, which refuse internal network addresses, so the tool can't be used to probe your own server's private network.

A quarterly audit routine

1. Run your homepage and top ten landing pages through the analyzer.
2. Note anything marked as a problem and fix the ones that affect several pages first, such as theme-level heading issues.
3. Check one example of each content type: a post, a page, a product and a category.
4. Run the pages ranking just above yours for your most important searches, and compare.
5. Re-run your pages after changes to confirm the fixes are live.

Over time, most issues the analyzer finds will be one-off fixes to your theme or settings. Once they're solved, they stay solved across every page.

Reading the results with judgement

Every check has a sensible default, but not every page needs to pass every one. A contact page doesn't need 300 words. A landing page built for one action may have few links on purpose. A short title can be the right title if it says exactly what the page is. Treat the analyzer as a checklist that points you at things worth a second look, then decide for each page whether the finding matters. The checks that almost always matter are the ones about indexing: the status code, the robots tag and the canonical. If any of those are wrong, the page may not appear in search at all, and that's the first thing to fix.

Fixing the most common findings

Missing or duplicate H1

Most themes print the post title as the H1. If the analyzer finds two, look for a site name or logo wrapped in an H1 in the header, or a page builder heading set to H1 inside the content. Change the extra one to a lower level or plain text. If it finds none, your theme may hide the title on some templates; check the theme's page settings.

Title too long or too short

Open the page in the editor and adjust the SEO title in the Rilea SEO panel, watching the pixel-width meter. If many pages have the same problem, change the title template in Rilea SEO, then Settings, then Titles & Meta, so they're all fixed at once.

No meta description

Write one in the Rilea SEO panel, or set a description template for the post type so every page has a reasonable default. The bulk editor is the fastest way to fill in many at once.

No structured data

Check that schema output is enabled in Rilea SEO's settings, then clear your cache and run the analyzer again. If it's still missing, another plugin or the theme may be removing the head output.

Missing canonical

Rilea SEO prints a canonical tag on every indexable page. If the analyzer can't find one, another plugin may be removing it, or the page is being served by something other than WordPress.

Not compressed

Compression is a server setting. Most hosts turn on gzip or Brotli by default; if yours hasn't, ask your host or use a caching plugin that enables it.

Many script and stylesheet files

Look at which plugins load files on every page. Many offer an option to load assets only where they're needed. A performance plugin can also combine or defer files. Re-run the analyzer to see the difference.

Comparing before and after

The analyzer doesn't store history, so keep a note of the results for your key pages before you make changes. A simple spreadsheet with the date, the page and the checks marked as problems is enough. When you re-run the analyzer after a fix, you'll see exactly what improved, and you'll have a record to share with a client or colleague.

For agencies, running the analyzer on a prospect's homepage is also a quick way to start a conversation: a short list of concrete issues, each with a clear fix, shows what you'd improve before any work begins.