Browser extension
The Smileline Chrome extension puts a free on-page SEO report, structured data checks, Google and Bing result tools, a live tag checker and YouTube transcripts one click away — and, signed in, patient and lead search, texts and leads from any page, notes for your team, your website's heatmaps, social posts from videos and your practice dialer.
The Smileline extension for Chrome is a free SEO toolbar. Open it on any page — your own site, a competitor's, a directory listing — and it reads what search engines see. None of the toolbar features needs a Smileline account, and while you are signed out the extension sends nothing about your browsing to Smileline.
Signed in, a few features read your practice's own data from Smileline: the
labels on your site and your competitors' in Google results, the
heatmap on your own website, Compare with
Smileline in the Tags tab and Fix with my practice details in the
Schema tab. With SEO — billed by use on
pay-as-you-go, or the
SEO & Ads add-on on the
older price list —
Show domain strength, Show
keyword data and Get volumes look things up from your practice's SEO
allowance, and only when you click them (see Google and Bing
results), and Is it indexed? in the Technical
tab sends the address of the page you're on to Smileline, which asks Google
Search Console about it, only when you click it (see Is it
indexed?).
With AI — priced per AI call on
pay-as-you-go, or the
AI assistant add-on on the
older price list —
Make posts on a YouTube video sends the
video's title and transcript to Smileline to write social posts, only when
you click it (see YouTube videos). While the side panel's
Notes tab is open, it sends the address of the page you're on, without
anything after a ? or #, to read and save your team's notes on it (see
Notes on any page). The Practice tab and the
address bar's sl keyword send what you search for, and Text and
Add as a lead send what you write and click to send (see Your
practice in Chrome). Nothing else about your
browsing is sent.
Three toolbar features ask outside services about a site, each only when you click it, straight from your browser: Look up the domain in the Technical tab sends the page's domain name to two public services, rdap.org and Cloudflare's DNS (see The page's domain); Check real visitors sends the page's address, with the Google API key you add in the settings, to Google's PageSpeed Insights (see Real visitors' Core Web Vitals); and the Tools tab's IndexNow sends the addresses you submit, with your IndexNow key, to IndexNow (see IndexNow).
Anyone on a practice's team can sign the extension in to Smileline — see Sign in. With Smileline Voice and a role that can make calls, you can also take calls straight from the toolbar — see the dialer below. Where Passwords is on for your practice, the popup also fills your practice's saved logins into the sites you sign in to — see Passwords.
Install
Open the Smileline listing on the Chrome Web Store and click Add to Chrome.
Click the puzzle-piece icon in the Chrome toolbar and pin Smileline so it stays visible.
The SEO report
Click the Smileline icon on any page. The popup shows the page's score out of 100 and how many problems are critical or worth improving. Click Open full report to open the full report in Chrome's side panel, beside the page.
The report is worked out in your browser. While you are signed out nothing about the page is sent to Smileline; signed in, the panel's header also shows your practice's name.
The side panel
The top of the panel shows the page's address and title, its score with a word for it — Good, Needs work or Poor — and how many checks are critical, to improve and passed. Under that you'll see the HTTP status, whether Google may index the page, how long it took to load and when it was checked. Whether Google may index it comes from the page's robots meta tags and robots.txt and, once you've checked what the server sends, its X-Robots-Tag header. Click Check again after you change the page.
The score starts at 100 and drops for each problem, more for serious ones. A page with any critical problem can't score Good.
The report follows you: switch tab or open another page and it reads the new page, as long as it is allowed to (see Analyse every page you open).
Signed in, This page and Practice at the top of the panel switch between the report and your practice's tools.
The tabs
- Overview — Fix first lists the most important problems. Each one says why it matters and, where the fix is markup you can paste, offers Copy fix (for example a canonical tag, a mobile viewport tag, Open Graph tags, or Dentist schema filled in with the practice name and phone number from the page). Images without alt text, images that don't load and broken links offer Show on page, which scrolls to them and outlines them in red. On Google previews the search result, with the title's width (Google cuts titles at about 580 pixels) and the description's length, and At a glance sums up words, headings, links, images and the two main Core Web Vitals.
- Content — the title and meta description with their lengths, every heading in order with skipped levels marked, word count, reading ease and the most repeated one-, two- and three-word phrases. Show headings on the page labels every heading on the page with its level; click a heading in the list to scroll to it. Type a Target keyword and click Check to see whether it appears in the title, the meta description, an H1 and image alt text, and whether it makes up at least 0.8% of the page's words. Whole words count, so "implant" doesn't match "implants".
- Links — internal, external, nofollow, sponsored and UGC counts. Internal
means your own domain and its subdomains, so
book.yourpractice.co.ukcounts as yours. Click a kind to outline those links on the page, and click it again to clear it. See Check the links. - Images — every image with its alt text, title, real and displayed size,
format and whether it loads lazily, filterable to those without alt text,
without a title or that don't load. A lazy-loaded image is listed by the
file it will load (its
data-src,data-lazy-srcorsrcset), and CSS background images lists the pictures the page's styles draw, with Show to outline them. Check file sizes lists the images' file sizes, biggest first, with their total; Chrome first asks to let Smileline read the sites the images come from. An image whose address redirects isn't followed, so its size shows as not reported. - Schema — the page's structured data, checked against what Google asks for, as a graph, a tree or code — see Structured data.
- Social — a preview of the card Facebook, WhatsApp and LinkedIn show when the page is shared, and every Open Graph and Twitter tag.
- Technical — HTTP status, HTTPS, robots meta tags, the robots.txt
verdict and the sitemaps it lists (Look for /sitemap.xml asks the site
for
/sitemap.xmland/sitemap_index.xmltoo), canonical tags, language, mobile viewport, character set, favicon, hreflang entries and any files loaded insecurely over http://. robots.txt rules are matched against the page's address with its query, as Google matches them. What the server sends and Check a list of addresses check what the server answers — see What the server sends — and Is it indexed?, Real visitors' Core Web Vitals, Browse as and Domain are there too. - Speed — Largest Contentful Paint, Cumulative Layout Shift, First Contentful Paint and time to first byte, plus Interaction to Next Paint once Chrome has timed a slow click or key press on the page, each against Google's good threshold, and the loading times and the page's files by type and size. These are measured in your browser on this visit, so they vary with your connection.
- Tags — the analytics, advertising and consent tags on the page: Smileline website tracking, the Google tag, Google Tag Manager, Meta pixel, TikTok, Microsoft UET, LinkedIn, Hotjar, Microsoft Clarity, Google consent mode and cookie banners, with their IDs. A tag set up twice is flagged, because it counts every visit twice. To see what the tags actually send, record a visit.
- Tools — tidy a list of web addresses and open it in tabs — see URL tools — and tell search engines that pages changed — see IndexNow.
- Notes — signed in, your team's notes on the page, highlighted on it — see Notes on any page.
Export at the bottom of the panel copies the whole report as text, to paste into an email, or as CSV, one row per check, for a spreadsheet.
The report reads the page as it is rendered in your tab. The server's response headers and raw HTML are read only when you click Check the server's answer in the Technical tab; until then, checks that need them are left out rather than guessed.
Check the links
The Links tab checks every link's HTTP status.
- Check links to this site tests the page's links to its own address, 100 at a time; Check the next carries on with the rest. It lists the broken ones — those that answer with an error, or don't answer at all — with Show on page. A link that redirects isn't broken, but the page can't see where a redirect leads, so it isn't followed there: Follow the redirects follows each one hop by hop and says where it ends up (Chrome first asks to let Smileline read every site and see its requests). A link that doesn't answer within 8 seconds, or whose site turns the check away (too many requests), isn't counted as broken: it's listed as one that couldn't be checked, so check again later. The report only counts the page as having no broken links once every one has been checked and answered, its redirects followed.
- Check links to other sites tests the rest — other sites, and your own site's other addresses such as a booking subdomain — 50 at a time, two at once with a pause between, without your cookies, following redirects hop by hop. Chrome first asks to let Smileline read every site and see its requests.
- No check ever goes into your own computer or network: a link, an image or
a redirect that points at an address such as
localhost,192.168…or a local name likeprinterisn't requested, and is listed as not checked. - All links lists each link with its anchor text, type,
relvalues and, once checked, its status; Broken filters to the broken ones. Download CSV saves the list as a spreadsheet.
Structured data
The Schema tab reads every JSON-LD block on the page — the same blocks the score's structured data checks read, so a Dentist block the tab shows is never missed by the score.
- Structured data says whether the page has Dentist or LocalBusiness schema and, if not, offers Copy fix with the practice name and phone number from the page.
- Google rich results checks each entity against Google's structured data guides: what's Required for the rich result, what's Recommended, and notes. For a dental practice that covers the business itself (address parts, a phone number with its country code, opening hours, a map position to five decimal places), organisations, people, breadcrumbs, reviews and star ratings, articles and image licences. Review stars a practice publishes about itself are marked: Google doesn't show those self-serving stars. Google no longer shows FAQ rich results, so FAQ markup is marked too.
- JSON-LD shows the blocks as a Graph — each entity a dot coloured by
its type, each property a labelled arrow, and entities that point to each
other by
@idjoined up — or as a Tree you can open level by level, or as Code, Pretty or Minified, with Copy JSON and Copy as<script>, and Download .json or Download .html (a page holding just that block, ready for a validator). In the graph, click a type to show only those entities and what they link to, move the Depth slider to hide entities nested deeper than you need, drag to move around, and use Zoom in, Zoom out and Fit. Download PNG and Download SVG save the drawing. A very large schema draws its first 1,200 entities and 2,500 links and says how many there are. - Check your own JSON-LD checks markup before it goes live: paste JSON-LD, or a page's HTML with its JSON-LD scripts, and click Check it. Back to this page's returns to the page.
- Microdata lists each microdata type on the page with how many items declare it and the properties they have. Microdata counts towards the Dentist check, but only JSON-LD is drawn and checked for rich results.
Fix with my practice details
Signed in, Your practice's details offers Fix with my practice details. It builds Dentist markup from your practice in Smileline — the location's name, address, phone number, confirmed map position and opening hours, your website and social profiles, your logo and the practitioners who work there — and lists it next to the page's own, property by property: Same, Different, Not on the page or Only on the page. Choose the location if your practice has more than one.
Click Copy Dentist markup and paste it in place of the page's own Dentist or LocalBusiness block. Smileline never changes your website. If the location is missing part of its address, the tab says what to add in Smileline first.
What the server sends
In the Technical tab, Check the server's answer fetches the page the way a crawler does — without your cookies, before any JavaScript runs — and shows:
- Status — the page's HTTP status and every redirect on the way, with a redirect loop or a chain of more than 10 redirects (where Google gives up) called out.
- X-Robots-Tag — the header's directives for Google, including
noindex. Anoindexornofollowhere counts in the page's score, its findings and whether it shows as indexable, just like a robots meta tag. - Raw HTML and the rendered page — whether the title, meta description, H1, robots meta tag and canonical are the same before and after JavaScript runs. Google indexes what scripts add, but later and not always, so a canonical that JavaScript adds, changes or removes counts in the page's score.
- Compare the source — the raw HTML the server sent next to the page as JavaScript left it, side by side when the panel is wide enough, with the lines that differ marked: red for what's only in the raw HTML, green for what only JavaScript added. HTML compares the markup element by element, so quoting and spacing don't count; Text compares only the words a visitor reads. Copy and Download take either side whole. A very large difference is compared on its first 2,000 lines a side.
The first time, Chrome asks to let Smileline read the site and see its requests.
The page checks also look at tracking parameters: a canonical that keeps
utm_source, gclid, fbclid or a session ID names one tagged copy of the
page instead of the page, and the fix to paste drops them.
Check a list of addresses checks many pages at once. Paste addresses, one
per line; repeats, lines that aren't web addresses and, if you type
something under Only addresses containing, addresses without it are left
out. To check redirects, put where each address should end up after it, as
from, to (a comma, a tab or a space; to may be a path such as /fees),
or click Import a CSV file with the addresses in its first column and
their targets in the second. Click Check them: each address's status and
redirects follow, 50 at a time, and Check the next carries on with the
rest. A row with a target shows Pass when it ends at that address and
the page there answers, and Fail with the reason otherwise. Download
CSV saves the results. This needs Chrome's permission to read every site,
which it asks for on the first check.
Is it indexed?
Signed in, on a page of your practice's own website, the Technical tab offers Is it indexed?. Click it and Smileline asks Google Search Console's URL Inspection about the page, through your practice's Search Console connection, and shows Google's answer in plain words:
- Google — whether the page is indexed and can appear on Google, with Search Console's own words for it, such as Submitted and indexed or Crawled - currently not indexed.
- Last crawled — when Google last crawled the page, or Never.
- Canonical — whether Google uses the canonical the page declares, or chose another page, which it names.
- Page fetch, Indexing, robots.txt and Crawled as — whether Google could fetch the page, whether a noindex tag or header keeps it out, what robots.txt says, and whether Googlebot crawled it as a phone or a desktop.
- Rich results — the rich result types Google found, with their errors and warnings.
Open the page's report opens the page's inspection in Search Console. Anyone on the team who can see SEO in Smileline can ask, not only the person who connected Search Console. It's free: Google answers up to 2,000 inspections a day for a site, and after that the panel says so until Google's day starts again at midnight Pacific time.
If your practice hasn't connected Search Console, or hasn't chosen its site yet, the panel says so with a link to Search visibility. A page that isn't on the site you connected can't be inspected. Google's Indexing API, which asks Google to crawl a page, only accepts job-posting and livestream pages, so the extension doesn't use it.
Real visitors' Core Web Vitals
Check real visitors in the Technical tab asks Google's PageSpeed Insights what Chrome users measured on the page over the last 28 days, on phones: Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint at the 75th percentile, each marked Good, Needs work or Poor by Google's lines (2.5 s and 4 s, 0.1 and 0.25, 200 ms and 500 ms). These are the measurements Google ranks on; the Speed tab measures only your own visit. This page shows the page's figures and Whole site its website's, and either says Not enough visitors for Google to say when Chrome hasn't recorded enough visits.
Google answers these checks only with a free Google API key, which you add once in Smileline's settings (the gear in the side panel), under Real-visitor data:
- In the Google Cloud console, create a project or choose one.
- Enable the PageSpeed Insights API for that project.
- Under APIs & Services → Credentials, create an API key and restrict it to the PageSpeed Insights API.
- Paste the key under Real-visitor data and click Save.
Without a key, the panel asks Google once anyway, and if Google turns the check away it says a key is needed, with a button to the settings. If Google refuses your key, the panel says so: check the key, and that the PageSpeed Insights API is enabled for its project. Remove deletes the key.
The request goes from your browser to Google only when you click, so Google sees the page's address — and your key, which goes nowhere else. Nothing goes to Smileline, and it works signed out. The key is kept in your browser, where web pages can't read it. Google can take up to a minute to answer. Pages on your own computer or network aren't sent.
Browse as Googlebot or a phone
Browse as in the Technical tab reloads the tab sending another browser's User-Agent — Googlebot smartphone, Googlebot desktop, Bingbot, iPhone Safari or Android Chrome — so you see what the site sends Google's crawler or a phone. The first time, Chrome asks to let Smileline change the requests the tab sends to the site. While it's on, the top of the report says so, with Turn off; it also ends when you choose Chrome (off) or close Chrome. It changes only that tab, and only on sites you've let Smileline read; the page's own scripts still see Chrome.
The page's domain
Domain in the Technical tab looks up the page's domain when you click Look up the domain: its registrar, when it was registered and when it expires, its status and name servers, and its DNS records (A, AAAA, CNAME, MX, NS and TXT).
The lookup goes from your browser to two public services: rdap.org, which passes it to the domain's registry, and Cloudflare's DNS service. They see the domain name you look up. Smileline isn't involved, and nothing is looked up until you click.
URL tools
The Tools tab tidies a list of web addresses:
- Grab this page's links fills the box with every link on the page, and Grab my open tabs with the address of every tab you have open (Chrome asks to let Smileline read them the first time, unless it may already read every site).
- Paste or edit the list, then choose Remove repeats, Remove tracking
parameters (
utm_,gclidand the like), and words to keep or remove. The clean list updates as you type; Copy copies it. - Open in tabs opens the clean list in new tabs, one after another, once you confirm how many. Stop stops it.
IndexNow
IndexNow in the Tools tab tells Bing and the other search engines that take part in IndexNow that pages on the site changed, so they crawl them sooner. Google doesn't use IndexNow.
- Make up an IndexNow key — 8 to 128 letters, digits or dashes — and put a
plain text file holding just the key on your website. By default it is
named after the key with
.txt, at the root of the site:https://www.yourpractice.co.uk/<key>.txt. - Enter the key and, if the file is somewhere else on the site, its address under Key file address. A key file in a folder covers only the addresses in that folder and below it.
- Click Submit this page, or put addresses in the URL tools' box and click Submit the list. Only addresses on the site you're on are sent; the panel says how many it left out.
The panel shows IndexNow's answer: Submitted (200), Received while IndexNow checks your key file (202), or why it refused: the request isn't valid (400), the key isn't valid because IndexNow couldn't find the key file or the key in it (403), the addresses aren't on the site or the key doesn't match the key file (422), or too many requests (429). IndexNow takes up to 10,000 addresses a request; a longer list goes in several, one after another.
The key is kept in your browser for that site, where web pages can't read it. Submissions go from your browser straight to IndexNow (api.indexnow.org), only when you click; Smileline isn't involved, and it works signed out. The first time, Chrome asks to let Smileline send to api.indexnow.org.
Analyse every page you open
The side panel can read a page only when you have let it. There are two ways:
- Click the Smileline icon on a page. That gives the extension access to that page only, until you leave it.
- Analyse every page you open. When the panel can't read a page it shows this button. Click it and Chrome asks you to let Smileline "read and change all your data on all websites", Chrome's wording for any extension that may open pages to read them; the report only reads. Allow it and the report follows you from page to page. You can take this back at any time in Chrome under Extensions → Smileline → Site access.
- In Smileline's settings. Click the gear in the side panel and, under Site access, click Allow every site. The Google results bar's Allow every site opens the same settings.
Chrome doesn't let any extension read its own pages (such as settings or a new tab), other extensions' pages or the Chrome Web Store, so the panel says it can't analyse those.
Record a visit
The Tags tab can also show what your tags actually send while you use the page — the page views, form submits and conversions Google, Microsoft, Meta and TikTok receive.
Open the Tags tab and click Record this visit. The first time, Chrome may ask you to let Smileline read your data on all websites: recording needs it to see the requests your tags make, and it only watches them, never changes them.
Click Reload the page to catch what it sends as it loads, then use it: open pages, click the buttons patients click, send a test enquiry.
Read the Timeline — every hit with its tag ID and key details (the consent state Google and Microsoft were sent, Meta's advanced matching, how long each tag's library took to load), the pages you opened, redirects and tag requests that never loaded — and the problems listed above it. Hits so far counts them per platform. Click Stop recording when you're done.
While it records you can also:
- Pick the conversion button. Click it, then click the button or link that means a conversion on the page — Book now, Send — as a patient would. The click goes through as usual; the panel shows the button's CSS selector (for a tag manager's click trigger) and whether a conversion hit followed it within 15 seconds. Press Esc to cancel.
- Record from page load. Tick it to catch the tags' very first calls as the site's pages load, from the next load on. It's off again when you stop recording or close the panel, and side panels in other windows keep their own. If Smileline can't keep it on — it lost access to every site, or couldn't set it up again after restarting — the panel unticks it and says why.
- Test a UET goal. Type a Microsoft Advertising goal — a destination URL that equals, begins with, contains or matches a pattern, or an event's category, action, label and value — and see which recorded UET hits meet it.
- Open dataLayer variables for the latest value of each key the page pushed to its data layer, as Google Tag Manager's variables read them.
The recording checks for:
- Doubled events — the same page view, conversion or event sent twice at once, which counts it twice.
- Missing consent mode — Google and Microsoft hits sent without their consent signal, which ads measurement in the UK and EU needs.
- Wrong tag IDs — an ID that isn't shaped like the platform's own, such
as an old
UA-ID in place of aG-one, or a placeholder left in. - Lost click IDs — a redirect that drops
gclid,msclkid,fbclidorttclidfrom the address, so the ad platform can't credit the click. - Microsoft UET details — the image-only tag in place of the JavaScript
one, a tag firing inside a frame, revenue that isn't a number, a
currency that isn't a three-letter code, product IDs and page types
Microsoft can't read, and the page's own
uetqevents checked against Microsoft's retail, hotel and travel parameters. - Meta pixel details — a Purchase without a value and currency, a
page address with an email address in it, the visitor's details sent
unhashed or as an event's details, data processing options, and the
page's own
fbqcalls: an unknown method, a non-standard event sent withtrack, aneventIDthat isn't text, a consent call Meta can't read. Messages Meta's own pixel library posts appear too. - Tags that can't send — a tag's address blocked by the page's Content Security Policy, a tag blocked by an ad blocker in your browser, or the browser being offline.
- The page's own tag code — a Google tag or Tag Manager snippet without an ID or with a placeholder one, no Google tag at all, a UET tag outside the page's head and body, two UET tags pushing to the same queue, the same UET tag as both JavaScript and an image (which counts every visit twice), and fallback image tags for a different ID. When you reload or open a page while recording, a UET tag, Meta pixel or Google Analytics ID the code sets up but that has sent nothing five seconds later is flagged.
- Enhanced conversions — the email, phone, name and address fields on the page's forms that Google Ads' enhanced conversions and Meta's advanced matching can use, and whether hashed user data was sent.
The recording stays in the side panel and ends when you close it.
Signed in, Compare with Smileline puts the page next to what Smileline set up: whether it loads your practice's own website tracking key, whether tracked calls go to the same Google Analytics property the page uses, and, for each ad platform Smileline sends conversions to, where they go and whether that's working (sent by Smileline's server). If your role can't see the website tracking settings or Ads, the panel says to ask an owner or manager.
Count the words you select
Select text on any page, right-click it and choose Count words and characters to see how many words and characters it has. Once the extension may analyse every page you open, the menu item itself shows the count, as Words: 120 · Characters: 734, before you click.
Google and Bing results
The extension numbers each organic result so you can read positions at a glance — useful when you're checking where your practice ranks for "dentist in ⟨your town⟩" without counting rows by hand. Later results pages carry on the count.
It works on google.com and google.co.uk from the start. On Google's other country sites and on Bing it starts once you've let the extension analyse every page you open.
The Smileline bar
Above Google's results, the Smileline bar sums up what the page shows: how many ads, whether there's a map pack, whether there's an AI Overview and which of the numbered results it cites, how many People also ask questions and how many organic results. It's worked out from the page in your browser; nothing is sent anywhere.
- Copy questions copies the People also ask questions, one per line, and Download CSV saves them as a spreadsheet.
- ⟨n⟩ places lists the map pack's businesses as the page shows them — category, rating and reviews, address, phone and website where Google shows them, and which are sponsored. Copy places copies them and Download CSV saves them.
- ⟨n⟩ AI Overview sources lists every page the AI Overview links to, with the result it is on this page where there is one. Signed in, your own site and your tracked competitors are labelled there too. Google hides where some sources link; those are matched to results by their title.
- Search as if in… runs the same search as if you were in another country or town. Pick the country, type the town as Google names it with its county or state — for example Leeds, England — choose the Google site to search (google.co.uk, google.it…) and, if you like, tick Only pages from this country or Only pages in its language, then click Search. Tick Keep for this tab's next searches and every search you make in that tab is asked the same way until you untick it or close the tab; on Google's other country sites this needs the extension to read every site. Use my location goes back to your own results (and stops keeping the place).
- Long-tail ideas asks Google's own suggestions around the search — with a wildcard before, after and between its words — and lists the phrases people type. It's free. Click one to search it; Copy ideas and Download CSV export them.
- Search intent shows, under each of the first ten results, what that page says it is: its title, meta description, H1 and H2 headings and its structured data types. Smileline reads the pages one at a time, in your browser, without your cookies; it needs you to allow every site (the bar's Allow every site opens the setting). Pages it has read are kept while the tab stays open, so clicking again reads nothing new. A result whose address Google hides can't be read. A page that redirects is followed only when Smileline can see where the redirect goes — once you've allowed what Record this visit asks for — and never to an address on your own network; otherwise its box says Redirects — not read.
Your site and your competitors
Signed in, results from your practice's website (the domain in its SEO settings) are labelled Your site, and results from the competitors you track in Search visibility are labelled with the competitor's name. The extension reads these from Smileline once per browser session, without using any of your SEO allowance.
Keyword data (SEO & Ads add-on)
Signed in to a practice with the SEO & Ads add-on and a role that can run SEO lookups, the bar offers Show keyword data. Click it to see the search's monthly searches, cost per click (in US dollars), keyword difficulty and paid-search competition — Low, Medium or High, how many advertisers bid on it — with a small line of its last 12 months' searches (hover it for each month), and up to eight related searches with theirs, for your practice's first location. Track in Smileline opens Search visibility. On Bing, a Smileline bar above the results offers the same Show keyword data for the search; the figures are Google's, and the bar says so.
Nothing is looked up until you click, and the bar says the most a lookup can cost before you do (about US$0.02). A lookup uses your practice's monthly SEO allowance; the same search is kept for 30 days, so showing it again is free. If the lookup is still running when the answer is due, click Check again — you aren't charged twice. The same goes for clicking again after Smileline was busy or couldn't be reached: it picks up the lookup you already asked for. Smileline runs one keyword lookup a minute for each location, so a click straight after another may say Smileline is busy; click again in a moment.
Get volumes for related searches
Below Google's results, People also search for and Related searches list more searches people make (Bing lists its own Related searches). With the same add-on and role, the bar offers Get volumes for them. Click it to see each one's monthly searches, cost per click, difficulty, paid-search competition and last 12 months. Before you click, the bar says how many it found and the most the lookup can cost: they are looked up together, up to 20 at a time, for at most about US$0.02. When a page lists more than 20, Get volumes for the next looks up the rest. Each search is kept for 30 days, so getting it again is free, and one with no figures shows dashes. Searches longer than 80 characters or 10 words have no volume data and aren't looked up.
Domain metrics (SEO & Ads add-on)
Signed in to a practice with the SEO & Ads add-on, a Show domain strength button appears above the results. Click it and each numbered result shows the domain's authority metrics — domain rank (0–1000), backlinks, and referring domains — under its title. Nothing is looked up until you click. Lookups come out of your practice's monthly SEO allowance; results are cached for two weeks, so looking up the same sites again is free. Sites still being looked up fill in as their figures arrive; while any are missing, or if Smileline couldn't be reached, the button stays as Check again, which carries on with the same lookup — sites already paid for aren't paid for again. Without the add-on (or signed out) the numbering still works and no button is shown.
YouTube videos
On a YouTube video, the extension can show the video's transcript beside it and, signed in, turn it into social posts.
Open the video, click the Smileline icon, and click Show on YouTube in Transcript and posts. Chrome asks to let Smileline read and change your data on www.youtube.com; this is needed once. (If you've let the extension analyse every page you open, the panel is already there.)
At the top of the column beside the video, click Show transcript.
The transcript comes from the video's own captions, read from YouTube in your browser; nothing is sent to Smileline. Choose another Language, or one of YouTube's translations, from the menu. Click a time to play the video from there. Copy with timestamps copies one line per caption, each starting with its time; Copy text copies it as one paragraph. A very long transcript is shown 500 lines at a time: the panel says which part you're reading, and Next part and Previous part move through it, while copying it and making posts use all of it. A video without captions has no transcript.
Turn a video into posts
Signed in to a practice with the AI assistant add-on, Turn it into posts writes three posts from the video's title, link and transcript.
Tick the channels the posts are for: Facebook, Instagram, LinkedIn or Google Business Profile.
To write about one part of the video, select that part of the transcript.
Click Make posts.
Each post offers Copy and Save to ideas, which adds it to your ideas board with the video's title. With Google Business Profile ticked and the SEO & Ads add-on, Save as Google post draft saves it as a draft on SEO → Google profile for your practice's first location; review and publish it there.
Writing posts uses the practice's AI allowance, shared with the rest of Smileline's AI, and only happens when you click Make posts. It needs a role that can create posts and use AI; the panel says plainly when the add-on is off, your role can't, or the allowance is used up for now.
Heatmaps on your website
Signed in, open the side panel on your practice's own website — the domain in its SEO settings, a page with Smileline's website tracking, or a site Smileline hosts — and click Show heatmap. A dark toolbar appears at the bottom of the page, and the clicks your visitors made are drawn on the page itself.
- Clicks or Scroll — where visitors click, or how far down they scroll, with the average fold and where 75%, 50% and 25% of them stopped.
- Desktop, Tablet or Mobile — the device, with how many recordings each has for this page.
- 7 days, 30 days or 90 days — the dates.
- The page's views, leads and bookings for the dates, and Recordings, which opens this page's heatmap and recordings in Smileline.
- ⟨n⟩ recent recordings — the page's latest recordings for the device and dates (up to 20), each opening that recording in Smileline in a new tab.
While you view a page's heatmap, your own visit to it stops being recorded, so reviewing your site doesn't add to its recordings.
Nothing is drawn until you click Show heatmap, and × removes it. The heatmap comes from Smileline's own website analytics, so it needs heatmaps and recordings switched on for your practice and a role that can see Ads. Clicks on parts of the page that have changed since they were recorded may not be drawn; the toolbar says how many of them it found. When the page changes while the heatmap is open — a menu opens, content loads in — the clicks are drawn again once it settles, and on a site that moves between pages without reloading, the heatmap follows to the new page.
Notes on any page
Signed in, the side panel's Notes tab holds your team's
page notes for the page you're on: comments on a
passage of its text, on one part of it, or on the page as a whole, with
their replies. Nothing is sent to Smileline until you open the tab. While it
is open, the panel sends the address of each page you view, without anything
after a ? or #, to read that page's notes.
Add a note
Select the text your note is about and click Add note in the Notes tab — or right-click the selected text and choose Add note, which opens the tab for you.
To note one part of the page instead, such as an image or a button, click Add note with nothing selected, then click that part of the page. Press Esc on the page, or click Cancel, to stop. For a note about the whole page, click Note on the whole page.
Type your note and click Save note.
A selection can be up to 1,000 characters. A part of the page nested too deeply to name can't take a note: pick a larger part, or note the whole page.
Highlights on the page
While the Notes tab is open, the passage each thread is about is highlighted on the page with a numbered pin, and a part of the page with a note is outlined. Click a pin to find its note in the panel, or click a note's number in the panel to scroll the page to it. The highlights go when you leave the tab, the page or the side panel.
Pages change, so each time the tab draws them Smileline looks for every passage again: where it was, then by its words — even if it has moved or a few of its words have changed. A note it can't find any more stays in the list, marked Not found on the page.
The highlights use the same access as the report (see Analyse every page you open). Without it the tab lists the notes and offers Show highlights, which asks Chrome for that access.
Reply, resolve and share
- Open shows the threads still to deal with, Done the resolved ones.
- Reply answers a thread, Resolve marks it done and Reopen brings it back.
- Edit and Delete show on your own notes — and, for owners, managers and your agency, on everyone's.
- Everyone on your practice's team sees a page's notes when they open it with the extension. To show them to someone without a Smileline account, an owner, a manager or your agency can click Copy share link: a view-only link to the page's open notes that works for 30 days. Copying a new link stops the old one, and Stop sharing ends it at once — see Share a page's notes.
Your Smileline website
On a page of your own Smileline website that has a note, the tab offers Open in website editor. It opens the page in the website editor on its Notes tab, where the AI assistant can draft the changes your notes ask for (see Ask the assistant to apply notes). Nothing goes live until someone publishes.
If the extension was signed in before page notes arrived, the Notes tab asks you to sign in again: in Options, click Sign out, then Sign in to Smileline.
Your practice in Chrome
Signed in, the extension finds your patients and leads, texts a number and adds a lead from any page. It acts as you: it offers only what your role can do, and when Smileline refuses something it says why in plain words.
Find a patient or lead
Open the side panel and click Practice at the top. Type a name, phone number or email address: matching patients and leads appear as you type, found the way the Patients search finds them. Click one to open their record in a new tab, or click Search in Smileline to see every match on the Patients page.
If you've selected text on the page, the tab offers Search “…” with the email address, phone number or name in it, so one click looks it up. The selection is read in your browser, with the same access as the report; nothing is sent until you search.
From any tab, type sl and a space in Chrome's address bar, then a name, number or email address. Your best matches appear as you type. Press Enter to open the first, or choose another. With no match, Enter opens Smileline's patient search for what you typed. Signed out, sl only offers to sign you in, and sends nothing.
Text a number or add a lead from a page
Select text on any page, right-click it and choose:
- Look up in Smileline — opens the Practice tab and searches for the email address, phone number or name in the selection.
- Text "…" with Smileline — opens a message to the phone number you selected. If your practice has more than one SMS or WhatsApp number, choose the one it goes from. Write the message and click Send: Smileline starts the conversation — or adds to the one you already have with that number — and opens it in a new tab. A WhatsApp chat the patient hasn't started needs an approved template, so start those from the inbox.
- Add as a lead — opens a lead form filled in from the selection: the name, mobile number and email address it finds. Check them, choose the treatment and, if you know it, the source, then click Add lead. Smileline adds it as New lead on Leads does: the person, then a journey for the treatment. If someone already has that mobile number or email address, it says so and links to them, so you can add the treatment from their record. Open the lead opens it on Leads.
Nothing is sent until you click Send or Add lead. Clicking Send again, unchanged, after Smileline couldn't be reached sends the same message — never a second one. If the person was saved but their treatment wasn't, Add lead sends only the treatment.
These menu items show only while you're signed in, and only the ones your role can use: looking up needs a role that can see patients, texting one that can send messages and see the practice's numbers, and adding a lead one that can create patients and journeys. A lead you add is yours, as one you add on Leads is.
Unread conversations on the icon
Signed in with a role that can see the inbox, the Smileline icon shows how many of your practice's conversations are unread, counted as the inbox counts them (99+ past 99). It updates when you open the popup or the side panel and, while calling is on, as messages arrive and conversations are read.
Sign in
Anyone on your practice's team can sign in, whatever their role. The toolbar features above don't need it.
Right-click the Smileline icon and choose Options (or click Sign in in the popup). Pick your practice region and click Sign in to Smileline.
A Smileline window asks you to approve the connection for your practice.
The extension then acts as you: it sees and changes only what your role allows, and anything it changes shows in the activity log under your name. To disconnect, click Sign out in Options, or remove the connection under Settings → Integrations → Apps in Smileline.
The dialer
With Smileline Voice enabled for your practice, the extension is also a softphone that stays registered while Chrome is open. Calling needs a role that can make calls; anyone else can sign in and use the rest of the extension.
Sign in, then click Enable calling in Options.
A Smileline window asks you to approve calling. Choose the practice the extension is signed in to. If your role can't make calls, Options says so and your sign-in stays as it was.
Allow the microphone when Chrome asks. This is needed once per browser.
Until calling is on, the popup's dialer says Calling off. If your role can make calls it offers Turn on calling, which opens Options; otherwise it says calling isn't available for your role, or that your practice doesn't have Smileline Voice on.
Once connected, the popup shows the dialer above the page summary:
- Incoming calls ring with a Chrome notification — with the patient's name when Smileline recognises the number — and can be answered or declined from the notification or the popup.
- Outbound calls start from the popup's dial pad, or by selecting a phone number on any web page, right-clicking it and choosing Call with Smileline.
- In a call you can mute, hold, hang up and send key tones. Closing the popup does not end the call.
- DND pauses ringing on this browser without signing out; calls continue to ring your other Smileline devices.
Signing out disconnects this browser's calling endpoint entirely — calls stop ringing here until you sign in again.
While you are on a call the popup offers Transfer: it lists every colleague who has calling set up, with their do-not-disturb state, and hands the caller to that colleague's most recently used device straight away.
A ringing or live call in the popup also shows Open in Smileline, which opens the matched patient's record — or the desk with the live call — in a new tab. When a call that was ringing you is answered by a colleague, the popup says Taken by and their name for a moment instead.
Passwords
Where Passwords is on for your practice, the extension fills your practice's saved logins into the sites you sign in to. It fills only when you click, only the page you are on, and never submits a form for you.
Passwords needs version 0.3.0 or later of the extension. Chrome updates the extension by itself.
Sign in, then click Turn on Passwords in Options or in the popup. A Smileline window asks you to approve it. Choose the practice the extension is signed in to. Calling, if you have it on, stays on.
Open the site's sign-in page and click the Smileline button in the toolbar. The first time after opening Chrome, enter your Smileline password and click Unlock.
Click Fill next to the login. Check what was filled, then sign in yourself.
The popup lists the logins saved for the site you are on. The site must
match exactly: a login saved for example.com is not offered on
login.example.com.
- Keyboard:
Ctrl+Shift+L(⌘⇧Lon a Mac) opens the popup, and Enter fills the first login listed. If another extension already uses those keys, set your own atchrome://extensions/shortcuts. - Two-step sign-ins: on a page that asks for the username first, Fill enters the username. Go to the next step and click Fill again for the password.
- One-time codes: on the page that asks for the code, Fill enters it. For groups shared with you as View or higher, the code is also copied after a fill, ready to paste.
- Copy and Copy code appear for groups shared with you as View or higher. Search all passwords finds those logins on any site, to fill one where it wasn't saved.
- Autofill only groups offer Fill alone, and only on the login's own site.
- Add this site's login saves a new login into a group you can edit.
The first time you use Passwords, or after your password was reset, the popup asks you to open Passwords in Smileline: your keys are made there.
Fill from inside the sign-in box
You can have a small Smileline mark appear inside the sign-in boxes of the sites you use, so you can pick a login without opening the popup.
- Open the extension's Options. Under Passwords, next to Fill from inside the sign-in box, click Turn on.
- Chrome asks to let Smileline read every site, unless you allowed that already. The mark can't be shown without it.
Then click in a site's username or password box, and click the mark. It lists
the logins saved for that site by name, with the username partly hidden.
Click one to fill it. From the keyboard, press Alt+↓ in the box, choose
with the arrow keys and press Enter.
- It is off until you turn it on here, even if you already allowed every site for the SEO report.
- It works on secure (
https) pages only. On anhttppage, fill from the popup. - It offers only the logins saved for the exact site you are on, and never fills when a page loads. A sign-in inside another site's frame gets no mark.
- On the page that asks for a one-time code, picking the login fills the code.
- If Passwords is locked, the menu says so: unlock it from the popup.
- Turn off in Options removes the mark; so does taking every-site access back in Chrome. Reload a tab that was already open.
Until you pick a login, the page you are on is told only the names of its own saved logins: no password, no code, and nothing saved for another site. Picking one puts that login's username and password (and its code, on a page that asks for one) into the page's boxes, as typing them would.
Offer to save a new login
With Fill from inside the sign-in box turned on, and Passwords unlocked, the extension offers to save a login you type yourself. Sign in to a site as usual. On the next page a small Save this login to Smileline? box shows the site and the username, partly hidden.
- Choose the Group (it starts on the one you saved into last) and click Save. Who can use the login follows from its group.
- If a login for that site already has that username with another password, the box asks Update the saved password in Smileline? instead, and names the login's group. Update saves the new password over the old one, which stays in the login's History. If someone changed that login in Smileline since, nothing is saved and the box says so: update it from the Smileline button.
- Not now closes the box. Never for this site also stops the offer there.
- There is no offer when the login is already saved, when the sign-in didn't go through (the page still asks for a password), on forms with more than one password filled in (such as changing a password), or when there is no group you can add logins to.
What you typed is kept in the extension's memory, for that tab only, for at most a minute, and only while Passwords is unlocked; closing the tab, locking Passwords or signing the extension out forgets it sooner. It is not written to disk and not sent to Smileline unless you click Save, and then it is encrypted like every other login. Chrome sometimes pauses the extension in that minute, and a few sites clear the sign-in form the instant it is sent: then no offer appears and nothing was kept. You can always add the login from the popup with Add this site's login.
A password typed with a username you already have saved is offered as a new login; it does not replace the saved one.
Use Smileline for passkeys
The extension can keep the passkeys you make on other sites with your practice's logins, so everyone who can use a login can sign in with its passkey.
Passkeys need version 0.4.0 or later of the extension. Chrome updates the extension by itself.
- Open the extension's Options. Under Passwords, next to Use Smileline for passkeys, click Turn on.
- Chrome asks to let Smileline read every site, unless you allowed that already. Passkeys can't be offered without it.
When a secure site then asks you to make a passkey, a Smileline passkey window opens:
- If Passwords is locked, enter your Smileline password, or click Use fingerprint.
- Choose where the passkey goes: Add to a login already saved for that site, or New login in a group you can edit.
- Click Save passkey. The site is told the passkey was made only once it is saved in Smileline.
When a site asks you to sign in with a passkey, the same window opens. It lists the passkeys saved in Smileline for that site: click one. If none is saved for it, the window says so: click Use another passkey. If Passwords is locked, unlock it there first. The window opens whether or not Smileline holds a passkey for the site, so the site can't tell either way until you answer.
- Use another passkey hands the request to Chrome's own prompt: your phone, a security key, or passkeys saved in Chrome. Cancel, or closing the window, tells the site no; Chrome's prompt doesn't open.
- Where a site asks you to confirm it's you, the window asks for your Smileline password or fingerprint first, even when Passwords is unlocked.
- If a site already has one of your passkeys saved in Smileline, the window says so and nothing new is made. Click OK to tell the site.
- If saving fails, click Save passkey again: it saves to the same place you chose, so the passkey never ends up in two logins.
- Making a passkey needs Edit on the login's group. Signing in with one works for anyone who can use the login, Autofill only included; the passkey itself is never shown to anyone.
- It works on the main page of secure (
https) sites. A passkey sign-in inside another site's frame, one offered in the username box as you type, one for a security key the site asks for by name, and a kind of passkey other than the most common (ES256) all go to Chrome's own. Smileline's own sign-in passkeys are always Chrome's. - To remove a passkey, open the login in Smileline, click Edit and remove it under Passkeys. Then sign in to that site another way.
- Turn off in Options stops it; so does taking every-site access back in Chrome. Reload a tab that was already open.
A passkey's private key is encrypted with its login, like a password: Smileline keeps it but can't read it. The site gets only what any passkey sends it: the passkey's public key when it is made, and a signature when you sign in. Exports leave passkeys out.
Unlock with a fingerprint
On a computer with a fingerprint sensor (Touch ID, Windows Hello), a touch can open Passwords in the extension instead of your password.
- Unlock Passwords once with your password, from the popup.
- Open the extension's Options and click Turn fingerprint on. Touch the sensor when Chrome asks.
After that, when Passwords is locked, click Unlock with fingerprint in the popup. It opens Options: click Unlock with fingerprint there, and Chrome asks for the touch (the popup would close under the prompt). Turn fingerprint off in Options removes it for this computer.
The extension's fingerprint is its own: turning the fingerprint on in Smileline's Passwords settings does not turn it on here, nor the reverse. Not every sensor can do this, and older versions of Windows can't: Options says so, and your password keeps working.
Anyone who can unlock the computer with its fingerprint or PIN can then open your passwords in this browser. Don't turn the fingerprint on for a computer account several people share.
When it locks
Passwords in the extension locks when you close Chrome, when you sign the extension out, and after your practice's lock time without using it. Click Lock in the popup, or Lock now in Options, to lock it yourself. Your Smileline password opens it again.
When your Smileline password is changed or reset, or your access to Passwords is taken away, the extension locks the next time it checks with Smileline. It checks before a fill, copy or save whenever its copy is more than 5 minutes old. A computer that can't reach Smileline keeps its copy for at most 24 hours.
What is and isn't filled
- A sign-in inside another site's frame is not filled.
- Pages Chrome keeps extensions out of, such as its own settings and the Chrome Web Store, can't be filled.
- Nothing is filled when a page loads, and no form is submitted.
What is sent
The extension reads your practice's logins from Smileline in their encrypted form and opens them in the extension, with keys your Smileline password unlocks. The address of the page you are on is not sent to Smileline. Each fill or copy is recorded against the login in your practice's activity log, under your name.
The Shop on the phone
Shop for dental supplies, check out, approve colleagues' baskets and follow your orders in the Smileline app for iPhone and Android, in the UK (except Northern Ireland) and the US.
Page notes
Pin notes for your team to any web page, reply and resolve them, and share a page's open notes with someone outside Smileline by a view-only link.