Website SEO audit β expanded checks and Mobile Usability detail
The Website SEO section of your local search audit report goes beyond a simple pass/fail β it scores five technical checks against your site, then surfaces richer detail when extended data is available. This article explains what each check measures, how to read the Mobile Usability and Lighthouse sections, and how the Page Speed bar factors into your score.
Audience: Owners and Managers who review local search audit results and act on website recommendations.
Before you begin
- You must have at least one active location in AI Digital Marketer.
- A local search audit must have been run for the location. If you have not yet run an audit, see Run local search audits (seo ranking).
- Some sections described below β Additional Checks, Mobile Usability, Lighthouse SEO Checks, and the Page Speed bar β appear only when extended SEO data is available for your site. If a section is absent, the audit ran on publicly available data only.
- The Website SEO detail view works the same way whether you are on a per-location audit detail page or viewing the SEO Audit β Organization Overview.
Steps
View the Website SEO section of your audit
- From the main navigation, select SEO Ranking.
- On the audit list, select the audit you want to review. If you are on the organization overview, select a location first, then open its audit.
- Scroll to the Website SEO section of the audit detail page. The section heading reads Website SEO and shows the points earned toward your overall score.
Read the five primary checks
The Website SEO category includes five scored checks. Each check shows a pass or fail indicator and the points earned.
The following table describes each check, its maximum point value, and what a passing result means.
| Check | Max points | Pass condition |
|---|---|---|
| Title Tag | 15 | A descriptive title tag is detected on your site's homepage. |
| Meta Description | 15 | A meta description is present. |
| Mobile Friendly | 20 | The site has a viewport tag and no Lighthouse-flagged mobile issues. |
| Schema Markup | 20 | Structured data (schema) is found on your site. |
| SSL Certificate / HTTPS | 10 | Your site serves over HTTPS with a valid certificate. |
Note: Points are deducted proportionally when a check fails or partially passes. A site that has a viewport tag but has Lighthouse-flagged mobile issues will not show a passing indicator for Mobile Friendly, and its score will reflect the deduction.
Read character count and quality labels (Title Tag and Meta Description)
When extended SEO data is available, the Title Tag and Meta Description checks show additional detail alongside the pass/fail indicator:
- Character count β the number of characters detected in the tag, for example "72 chars."
- Quality label β a plain-English assessment such as "Good," "Too short," or "Too long."
Use these labels to decide whether a title or description needs editing even if the check shows a passing indicator.
Read the Additional Checks section
When extended SEO data is available, an Additional Checks section appears below the five primary checks. This section does not contribute directly to your primary score but highlights technical details that affect search visibility.
The following table describes each item in Additional Checks.
| Check | What it measures | Pass condition |
|---|---|---|
| H1 tag | Whether exactly one H1 heading exists on the page | Exactly one H1 present |
| Image alt text | Percentage of images with descriptive alt text | 90% or higher |
| Open Graph tags | Whether Open Graph meta tags are present | Tags detected |
| URL | Whether the page URL is crawlable and clean | Pass |
| Sitemap | Whether a sitemap file is accessible | Detected |
| Robots.txt | Whether a robots.txt file is accessible | Detected |
| Heading hierarchy | Whether heading levels are used in order (H1 β H2 β H3) | No hierarchy issues |
Important: If the audit could not reach your sitemap or robots.txt β for example because of a network timeout or an access restriction β those items display a neutral "could not verify" marker. A "could not verify" result is not a failing red indicator and does not penalize your score. It means the check was inconclusive.
Read the Mobile Usability section
The Mobile Usability section appears when Lighthouse mobile audit data is present. It lists each individual audit item with a pass or fail indicator.
Understanding the lead-in message
Before the list of items, a lead-in message describes the overall mobile situation:
- No lead-in β all mobile checks pass. Your site is fully optimized for phones.
- "Your site works on phones, but a few things could be easier to use:" β the site is functional on mobile, but Lighthouse identified minor usability improvements.
- "Your site isn't fully optimized for phones:" β Lighthouse identified fundamental issues that affect how the site works on mobile devices.
Reading failed items
For each failed audit item, the section shows a plain-English explanation of why the check failed β for example, that tap targets are too small or that text is too small to read without zooming. Use these explanations to brief your web developer or to apply fixes using the auto-fix tools described in Run local search audits (seo ranking).
Note: The Mobile Friendly primary check combines a viewport signal with the Lighthouse mobile audit results. If your site has a viewport tag but Lighthouse flags issues, the primary check will show a failing indicator and your Mobile Friendly score will be docked β even though the viewport tag is present.
Read the Lighthouse SEO Checks section
The Lighthouse SEO Checks section appears when Lighthouse SEO audit data is present. It lists each Lighthouse SEO audit item with its title and a pass or fail indicator.
These checks cover technical SEO signals that Lighthouse evaluates automatically, such as whether the page is indexable, whether links have descriptive text, and whether the document uses a valid language attribute. Review any failing items and pass them to your web developer for resolution.
Read the Page Speed bar
The Page Speed: bar appears when a page-speed score is available for your site. It shows:
- A color-coded progress bar β green when the score is 80 or above, yellow when the score is 50 or above, and red when the score is below 50.
- The numeric score out of 100.
- The points earned toward your Website SEO score, out of a maximum of 20.
Tip: Page speed affects both your Website SEO score and your guests' experience. A score below 50 (red) warrants immediate attention. Share the Lighthouse SEO Checks section with your developer alongside the Page Speed result so they can address both at once.
Tips
- Act on the Additional Checks items even when your primary score is passing. A low image alt-text coverage percentage or a missing heading hierarchy can hurt accessibility and search visibility without triggering a primary check deduction.
- Run a new audit after making website changes. After your developer applies fixes, select Run New Audit from the audit list to get an updated score. Changes are reflected in the next completed audit only.
- Use the organization overview to compare locations. If your organization has multiple locations that share one website, the SEO Audit β Organization Overview shows the Website SEO results as a single view. Website changes apply to your site as a whole; completing an action there marks it done for the location you are viewing, and other locations' Website SEO checklists will reflect the fix at their next scheduled audit.
- "Could not verify" is not a failure. If sitemap or robots.txt items show a neutral "could not verify" marker, check that your hosting provider is not blocking audit probes with IP-based rate limits, and re-run the audit.
- Address red Page Speed scores before investing in other SEO work. A slow site reduces the effectiveness of improvements in every other category.
Troubleshooting
The Additional Checks, Mobile Usability, and Lighthouse SEO Checks sections do not appear.
Extended SEO data was not available when the audit ran. This happens when the audit probe could not fully crawl your site β for example, if your site requires authentication, blocks crawlers via robots.txt, or is hosted behind a proxy. Verify that your site is publicly accessible and that robots.txt does not disallow crawlers, then select Run New Audit.
The Mobile Friendly check shows a failing indicator even though the site has a viewport tag.
A viewport tag alone is not sufficient for a passing result. The Mobile Friendly verdict combines the viewport signal with Lighthouse mobile-usability results. If Lighthouse flagged any issues β even minor ones β the check will show a failing indicator and the score will be docked. Review the Mobile Usability section for the specific items Lighthouse flagged, and resolve those issues.
The Page Speed bar does not appear.
The page-speed score requires a successful Lighthouse run against your site. If Lighthouse could not complete β for example, due to a timeout or a JavaScript error that prevents page load β the bar will be absent. Ensure your site loads successfully in a standard browser without login and re-run the audit.
The sitemap or robots.txt item shows "could not verify" instead of a pass or fail.
The audit probe could not reach these files during the audit run. This does not count as a failure. Common causes include server-side rate limiting, firewall rules blocking the probe's IP range, or temporary downtime. Re-run the audit to attempt verification again.
The character count and quality label are missing from the Title Tag or Meta Description check.
These labels appear only when extended SEO data is available. If they are absent, the audit ran on limited public data. Running a full audit with your site publicly accessible should surface this detail.
Worked example
Example: After running an audit on a spa's website, the Website SEO section shows the following results:
- Title Tag β 11/15 pts β "48 chars β Good" β passing indicator
- Meta Description β 0/15 pts β "12 chars β Too short" β failing indicator
- Mobile Friendly β 10/20 pts β failing indicator (viewport tag present, but Lighthouse flagged tap targets that are too small and content wider than the screen)
- Schema Markup β 20/20 pts β passing indicator
- SSL Certificate / HTTPS β 10/10 pts β passing indicator
- Page Speed: β score 62/100 (yellow bar) β 12/20 pts
The Mobile Usability lead-in reads "Your site isn't fully optimized for phones:" followed by two failed Lighthouse items: tap targets are undersized and the viewport forces a horizontal scroll. The Additional Checks section shows image alt-text coverage at 74% β below the 90% threshold β and the sitemap item shows "could not verify."
The owner shares the Mobile Usability detail with their developer, updates the meta description to 140β160 characters, and schedules an image alt-text audit. After fixes are applied, they select Run New Audit to confirm the improvements.