Check your website
Check every page of your website, read its Health, AI search and Speed scores, work through what to fix and send each fix to your web developer.
Open SEO → Website. Smileline reads every page of your practice website, up to 10,000 pages, runs 338 checks on them and lists what to fix, worst first. This page shows you how to run a check, read its scores, work through the issues and send a fix to your web developer.
Under the page title you see the domain that was checked, when the latest check finished and how many pages it read, such as 1,240 of 1,240 pages. The page has six tabs:
- Overview: the three scores, the crawled pages, what to fix first, the reports and how Health has moved over time.
- Issues: everything the check found, with what it means and how to fix it.
- Crawled pages: every page Smileline read and what it found on each.
- Statistics: your site in figures, from status codes to AI bots.
- Reports: a score for each area, such as HTTPS or Core Web Vitals.
- History: earlier checks, and any two compared.
Add the website domain
Smileline checks the website saved under Settings → Practice details unless you confirm a different primary domain in SEO settings, at the top of the page.
If neither is saved yet, Setup on the right of the Overview tab asks for one. If your role can manage SEO, enter the website's domain, such as example.co.uk, and click Save. You can paste the full address; Smileline keeps only the domain. If your role can't manage SEO, Setup says that someone who manages SEO needs to add it.
Once a domain is saved, Setup shows it, Checked monthly and whether speed checks are on.
Check the website
Smileline checks your website once a month by itself. To check it now, for example after your developer has made a fix, click Check website at the top of the page. You need a role that can manage SEO.
- You can start a check yourself once every seven days. A check that failed or was cancelled doesn't count, so you can start again straight away. The monthly check doesn't count either.
- Each check counts towards your practice's monthly SEO usage limit (see Watch this month's usage). When the limit is reached, a new check doesn't start.
A check reads up to 10,000 pages, starting from your home page. On a larger site, the line under the title shows how many it read out of how many it found, such as 10,000 of 14,200 pages, and every tab covers only the pages it read.
Smileline opens each page the way a browser does, running its JavaScript, and also reads the page as your server sends it. That way it can tell what search engines and AI tools that don't run JavaScript see. A page marked noindex is read only as your server sends it, so the checks that compare it with and without JavaScript aren't run on it. The check doesn't check or follow the links on a noindex page, so a page that only noindex pages link to isn't read, and a broken link found there before stays in To fix until it is checked. It also uses:
- Google PageSpeed Insights and the Chrome UX Report for speed, accessibility and Core Web Vitals. Setup shows Speed checks with Google when these are on. If it shows Speed checks need a Google key, those checks aren't run and the Speed score stays empty.
- Search Console, once it is connected (see Connect Google first), for what Google itself reports about your pages.
- Your Google profile, to compare the details on your website with the ones on your profile. These checks are coming soon; for now they show as not checked.
The list of checks shows which ones need each of these.
While a check runs, Checking your website above every tab shows the step it is on and how far it has got: Starting, Reading your pages, Collecting what was found, Checking each page, Measuring speed with Google, Working out the scores and Finishing. If Google's daily allowance of speed checks runs out, it says so and carries on by itself. If Google still can't measure a page after several tries, the check finishes without that page's speed: it shows —, and Check this page again measures it again. Until the new check finishes, the tabs show the last one that did.
If a check stops, The last website check didn't finish says why. If your role can manage SEO:
- Click Retry to carry on from the step where it stopped. The pages it already read aren't read, or paid for, again. Retry shows only when there is work left to resume and no other check is running.
- Click Discard to drop the stopped check. It shows as cancelled under Past checks, and nothing resumes it.
To start again from the beginning, click Check website.
Read the scores
The Overview tab opens with three scores out of 100. Each is rated Good (90 and over), Needs work (50 to 89) or Poor (under 50), and says how it moved since the check before, such as Up 3 since 4 Oct.
- Health: how healthy the site is overall, with how many checks found errors and how many found warnings. If some of your sitemap files couldn't be read, it says how many.
- AI search: how ready the site is to be found and quoted by AI answers such as ChatGPT, Claude, Perplexity and Google's AI. Under it you see how many AI search bots your robots.txt blocks and whether your llms.txt was found, is missing or has mistakes.
- Speed: the average Google PageSpeed score of the pages measured, tested as a phone, such as Phones, 12 pages. It says Not measured on this check when this check measured none.
How the scores are worked out
Health starts at 100. Each check that found an error or a warning takes a share off what is left:
- An error takes between 1.5% and 6%, and a warning between 0.5% and 2%. Errors weigh three times as much as warnings.
- Within that range, the larger the share of pages, links or files that failed out of those the check looked at, the more it takes. Five broken pages out of 500 cost less than five out of 10.
- Notices never count.
- A check that couldn't be done, such as a speed check without Google's figures, counts neither way. A check with nothing to look at doesn't count at all.
For example, two errors that each affect every page leave 100 × 0.94 × 0.94, about 88. Because each check takes its share of what is left, Health never drops to 0 and every fix raises it. Which checks fail matters more than how many pages they touch, so a large site isn't marked down for its size.
AI search is worked out the same way, but only from the checks marked AI search in the list of checks: AI search bots blocked in robots.txt, llms.txt, how the content is laid out, links, structured data and content that only shows with JavaScript. Each of them counts as an error, whatever its severity, because AI answers depend on them.
The AI search bots Smileline looks for in robots.txt are OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Googlebot and Google-Extended. Bots that only collect training data, such as GPTBot, ClaudeBot and CCBot, are your practice's choice, so blocking them isn't flagged.
Each report on the Reports tab is scored the way Health is, from its own checks (see Compare areas in the reports).
The rest of the overview
- Crawled pages says how many pages the check read and how many clicks from the home page the deepest one is. The bar splits them into Healthy, Have issues, Broken and Redirects. Click All pages for the Crawled pages tab.
- Fix first lists the issues to start with: errors first, then what affects most pages. Click All issues for the Issues tab.
- Reports shows the first nine report scores. Click a report to see its issues, or All reports for the Reports tab.
- Health over time draws one point per check once a second check has finished. Switch between Health, AI search, Speed and Issues.
On the right, Send to your developer says how many fixes you have emailed this month; click All emails to see every email, its status and its attempts. Setup is under it.
Work through the issues
The Issues tab lists every check that found something, grouped into Errors, Warnings and Notices, with how many of the checks that ran found something and how many issues are new since the check before. A red dot marks an error, amber a warning and grey a notice. Each issue says what was found and how often, such as 12 pages have no meta description, with its area under it. AI search marks an issue that counts towards the AI search score, and New one the check before didn't find.
To narrow the list:
- Click an area, such as Links or Security. Only areas with issues are shown; click + 4 areas with no issues for the rest.
- Choose All, Errors, Warnings or Notices.
- Choose To fix, Sent, Fixed or Hidden.
Click Export CSV for the list as it is shown: each issue's name, area, severity, how many were found, on how many pages and whether it is new.
Click How to fix on an issue to open it. The panel shows:
- its severity, area and tags;
- What it means: why it matters;
- How to fix: what to do, written so you can pass it on;
- Affected pages or Affected links, with how many, a page at a time. Each row names the page, the link or file on it where there is one, and what was measured, such as a status code. Click Load more for the next page.
If your role can manage SEO, click Send to developer to email the fix (see Send a fix to your developer) or Hide to move the issue to Hidden. Export CSV in the panel saves every affected page or link with what was measured.
Where an issue goes next
Each check that finds something is one issue, and it stays the same issue from one check to the next:
- To fix: found and not yet sent. An issue that was fixed and found again comes back here.
- Sent: you sent its fix to your developer.
- Fixed: a later check looked again at every page, link and file it was found on, and found nothing. The latest check's Fixed lists what that check fixed.
A check that didn't reach all of them, such as one that stopped at 10,000 pages, never marks the issue fixed. It stays where it was, marked Not checked again yet, with the figures from when it was last found, until a later check reads the rest. The same happens when a page didn't answer, or when a link on it couldn't be checked. A page you removed from your website counts as fixed once a check that read the whole site no longer finds it.
- Hidden: someone who manages SEO hid it.
Look at each page
The Crawled pages tab lists every page the check reached. Search for a page by its address or title under Search pages, or choose All, With issues, Broken, Redirects or Blocked. For each page you see:
| Column | What it shows |
|---|---|
| Page | The page's address and title |
| Status | The code your server answered with: green when the page loads, red for a redirect or an error |
| Issues | How many issues were found on it |
| Clicks deep | How many clicks it is from the home page |
| Link rank | How strongly your own pages link to it, out of 100: your best-linked page is 100 |
| Links in | How many of your pages link to it |
| Speed | Its Google PageSpeed score as a phone, coloured by rating, or — when Google couldn't measure it |
Click Load more for more pages, or Export CSV to save every page in the current view.
Click a page to open it. The panel shows its status, clicks from home, link rank, links in and out, word count, how much of it is text rather than code, its speed on a phone, whether it is in your sitemap, its canonical (Itself, another page or None) and its structured data. Under Found on this page are the issues on it, or Nothing to fix on this page.
Fixed something on a page? Click Check this page again in its panel instead of waiting for the next check. Smileline reads the page fresh, as a browser shows it, measures its speed on a phone again and reruns the checks on the page and its links. The button reads Checking this page… until it finishes, then the panel shows Checked again at with the time. The page's issues, your Health score, the issue counts and the Issues tab update with it, and an issue that was only on that page moves to Fixed. Checks that compare pages with each other, such as duplicate titles or pages nothing links to, keep their result until the next full check. If Smileline can't read part of the page this time — the page doesn't load, or it has more links than one read takes in — what it couldn't read keeps its earlier result, and an issue found there stays in To fix until it is checked. You can check a page again on the latest check only, and not while a check is running. Each one counts towards your monthly SEO budget, like the full check. If it can't finish, the panel says why, with Retry: it carries on from where it stopped, without paying again for what it already read. If a newer check finishes first, the panel says only the latest check's pages can be checked again.
See your site in figures
The Statistics tab sums the site up in eight tiles. A tile is left out when the check didn't collect its figures.
| Tile | The big number | Underneath |
|---|---|---|
| Status codes | The share of pages that answer with an error | The share answering 2xx, 3xx, 4xx and 5xx |
| Sitemap vs crawl | How many pages your sitemap lists | Pages crawled and in the sitemap, crawled but not in it, and in it but not linked from your site |
| Clicks from home | The share of pages more than 3 clicks deep | The share at each number of clicks |
| Links in | The share of pages linked from only one of your pages | The share by how many of your pages link to them |
| Markup | The share of pages without structured data | The share with JSON-LD, Open Graph, X cards and microdata |
| Canonical | The share of pages without a canonical tag | The share pointing to themselves and to another page |
| Languages | How many languages hreflang names, or no hreflang used | The share of pages in each language |
| AI bots | How many AI search bots are blocked | Whether ChatGPT, Claude, Perplexity and Google AI are allowed or blocked |
Compare areas in the reports
The Reports tab scores twelve areas out of 100, each from its own checks, the way Health is scored: Crawlability, HTTPS, International, Performance, Core Web Vitals, Internal linking, Markup, robots.txt, AI search, Accessibility, Local & compliance and JavaScript impact. Each card shows the score, coloured by the same bands as the overview's, and how many issues it has. A report reads Not checked when nothing in it could be checked, such as Core Web Vitals while speed checks are off.
Click a report to open the Issues tab showing only its issues. Click the report's name at the start of the area list to show every issue again.
- Accessibility: the accessibility checks are all notices, so they never move Health. This report scores them as warnings.
- Local & compliance: includes your practice's structured data, whether your website matches your Google profile, and tap-to-call, booking and a map. For practices in the UK it also looks for a link to the GDC, GDC registration numbers, how to complain and your CQC rating. Everywhere Smileline serves except the US, it also checks that tracking doesn't load before visitors agree to cookies.
Look back at earlier checks
On the History tab, Compare two checks shows what changed between two finished checks, check by check. Choose the earlier one under From and the later one under To. For each issue you see how many were found Before and After, and the Change: red when there are more, green when there are fewer. When one of the two checks couldn't measure an issue at all, such as speed without Google's results, that side reads Not measured and no change is shown. Checks made before the current website check have no per-check figures, so they can't be compared.
Past checks lists every check with its date, status, the pages it read and what it cost; a failed check says why, and a check stopped because your website address changed says so. Click Load more for older ones.
Send a fix to your developer
You need a role that can manage SEO. You can send an issue that is in To fix or Sent:
On the Issues tab, click Send on the issue, or open it with How to fix and click Send to developer.
Under Developer email, choose a saved contact or enter your developer's email address.
Click Queue email.
The first time you use an address, Smileline emails the developer to confirm it and the fix is not sent yet. The dialog tells you whether a new confirmation was sent or the address is still in its one-hour cooling-off period. Once they click the confirmation link, queue the fix again and it goes out immediately. Every later email to that address sends straight away.
A confirmation attempt is used up before Smileline asks the mail provider to send it, so an unavailable or unclear provider response still starts the cooling-off period. Each contact has three confirmation attempts in all. An address that uses all three without confirming stays in the list but can't be reset or deleted; use another address.
Each confirmation link works for seven days. After the one-hour cooling-off period, asking for confirmation again replaces the previous link with a fresh seven-day one, as long as the contact has an attempt left.
The contact list is shared with Articles. It shows confirmed, awaiting confirmation, confirmation limit reached and blocked contacts. Someone with permission can block a contact and remove that block later. A block reported by the recipient or their mail server is permanent and can't be removed.
Confirmation protects your practice's sending reputation: Smileline only emails developers who have agreed to receive them. If the recipient or their mail server blocks future email, Smileline shows only Blocked. Tagged variants of the same mailbox are also refused for your practice, so use a genuinely different address.
Each practice can send 20 developer emails a day and add up to 5 new addresses a day. Retrying the same failed send returns its original email and doesn't use another of the day's 20. A practice keeps up to 100 developer contacts; blocked and unconfirmed ones still count.
Smileline retries a queued email for up to 24 hours. If it still can't be handed off, it is marked failed; correct the address or the problem it names and send it again.
The email gives your developer:
- the issue's fix steps, the page and how many pages it affects;
- a starting point for the page's title, meta description and canonical link; and
- a
DentistandLocalBusinessstructured data (JSON-LD) example, with how to check it.
The structured data example uses only your confirmed practice and location details, never patient data. If the primary domain or the location's address is incomplete, the email leaves the example out and tells the developer what needs confirming instead.
Ask your developer to compare the suggested details with the live website before publishing, check the page once it is live, then click Check website again. Structured data doesn't guarantee that Google shows anything extra in search.