Our Understanding of Your Business
This is where we write what we know about your business from our search through your website and the internet.
Checked real Google ranking positions for 15 keyword(s) discovered from this site's own content.
Google's AI Overview appeared for 6 of 13 keyword(s) checked — this site was cited as a source in 1 of them.
| Keyword | Position |
|---|---|
| example business services | 4 |
| trusted local services | Not in Top 100 |
| get quote | Not in Top 100 |
| family owned operated | Not in Top 100 |
| serving the local area | Not in Top 100 |
| trusted local provider | 2 |
| example business services for sale | 2 |
| example business services near me | 4 |
| example business services Sydney | 4 |
| trusted local services for sale | Not in Top 100 |
| trusted local services near me | Not in Top 100 |
| trusted local services Sydney | Not in Top 100 |
| get quote for sale | Not in Top 100 |
llms.txt not found (optional) • No AI-answer schema found (optional)
See “AI Search Crawler Access” further down for the full bot-by-bot breakdown.
The score above is a technical checklist score, not an SEO performance score. It is calculated across 43 individual checks (homepage on-page checks, site-wide crawl findings, page speed, and local business listing, when available):
What this score does NOT include (because SecureNow has no access to the data required):
See "Not Assessed" below for what each of those would require. Treat this score as a technical hygiene checklist, not a verdict on how well the site is actually performing in search.
This scan crawled every page reachable by following internal links from the homepage — 6 page(s) in total (no page limit was applied), AND separately fetched all 5 URLs listed in the site's XML sitemap directly, regardless of internal linking (see “Full URL Inventory & Indexability” below for that complete picture). This appears to cover the site’s full linked structure, and (via the sitemap inventory) its full declared URL set too. A dedicated crawler (Screaming Frog, Sitebulb) can additionally handle JavaScript-rendered content and parameter-URL deduplication, which are outside this scan’s scope. Results are grouped into the sections below alongside the homepage findings.
1 title(s) are reused across multiple pages.
Why it matters: When multiple pages share the same title, search engines struggle to know which one to rank for a given search — pages can end up competing with each other instead of the competition. This is one of the more reliable, high-confidence findings an automated scan can make.
Potential impact if fixed: Giving each page a unique, specific title lets it compete for its own search terms instead of splitting visibility with near-identical pages.
Recommended fix: Click into each title below to see which pages share it, then rewrite the title on each page to describe that specific page (what makes it different from the others).
| Title | Used on |
|---|---|
| "Example Business | Sydney" | 2 page(s) — click to view |
No canonical tag found.
Why it matters: This tells search engines which version of a page is the “original” when similar or duplicate URLs exist (e.g. with and without “www”). This check only looks at the homepage — see “Canonical Tags (Site-Wide)” below for canonical health across all crawled pages.
Potential impact if fixed: Prevents search engines from splitting ranking credit across duplicate versions of the same page.
Recommended fix: Ask your developer to add one line of code to the page's <head> section telling search engines this exact page's own web address is the “original” version (this is called a canonical tag).
Found 1 JSON-LD block(s) with schema type(s): AutoBodyShop, PostalAddress. Commonly-valuable types not found (and where the page shows evidence they'd actually apply): Organization, LocalBusiness, WebSite (only worth adding if genuinely relevant to this business/page). No FAQPage, HowTo, Article, or QAPage schema found — adding one (where genuinely relevant, e.g. an FAQ section) can help AI Overviews and answer engines extract and cite direct answers from this content.
Why it matters: Structured data (JSON-LD) is a behind-the-scenes code format that helps search engines display extra information directly in search results — like star ratings, business hours, or FAQs. Simply having *some* JSON-LD present isn't the full picture; what matters is which schema @type(s) are used and whether they're complete and accurate. See the specific schema types found below.
Potential impact if fixed: Using the schema types most relevant to this business (e.g. LocalBusiness, Product, BreadcrumbList) can unlock “rich results” in Google that stand out visually and typically get more clicks than a plain listing.
Recommended fix: This is a technical, code-level task — ask your developer to add structured data (a behind-the-scenes code snippet called “schema markup”) for: Organization, LocalBusiness, WebSite, if relevant to this business. Validate any new markup in Google's Rich Results Test before publishing.
1 description(s) are reused across multiple pages. Lower priority than duplicate titles — descriptions don't directly affect rankings.
Why it matters: Identical descriptions across pages waste the opportunity to give each page its own compelling reason to be clicked in search results.
Potential impact if fixed: Writing a unique description for each page gives every listing its own click-worthy pitch instead of repeating the same one.
Recommended fix: Click into each description below to see which pages share it, then write a short, unique 1-2 sentence summary for each page describing what's actually on it.
| Description | Used on |
|---|---|
| "Example Business: trusted smash repairs, spray painting and insuran..." | 2 page(s) — click to view |
Checked 6 page(s) — both internally-linked pages AND orphaned sitemap pages fetched directly — finding: 6 missing a canonical tag, 0 using a relative (non-absolute) URL, 0 pointing to a different URL than themselves.
Why it matters: A canonical check limited to only internally-linked pages would silently skip orphaned pages entirely. This check covers every page found either by crawling links or by fetching the sitemap's full URL list directly.
Potential impact if fixed: Adding a self-referencing, absolute canonical tag to every indexable page is standard practice and removes ambiguity about which URL should rank.
Recommended fix: Ask your developer to add a canonical tag (a line of code pointing a page to its own full web address) to every page listed as missing one, and to fix any listed as using a shortened/partial address instead of the full one.
6 page(s) missing a canonical tag entirely:
Missing Open Graph tags: og:title, og:description, og:image (affects link previews on social media).
Why it matters: These control how the page looks when shared on Facebook, LinkedIn, and other social platforms — the preview image, title, and description.
Potential impact if fixed: A proper preview card can noticeably increase click-through when links are shared on social media instead of showing a blank or broken preview.
Recommended fix: Ask your developer to add a few lines of code that control how the page looks when shared on Facebook, LinkedIn, etc. (a preview image, title, and short description), so links don't show up blank or broken.
No favicon found.
Why it matters: The favicon is the small icon shown in browser tabs and bookmarks.
Potential impact if fixed: A small trust and brand-recognition signal, especially for visitors with several tabs open.
Recommended fix: Create a small square logo/icon image and ask your developer to set it as the site's favicon — the little icon shown in browser tabs.
Likely focus phrase “explore service” is missing from: title, H1 heading, opening paragraph.
Why it matters: This check guesses a likely topic phrase from the page's own text-frequency and checks whether it appears in the title, heading, and opening content. This is NOT keyword research — it has no access to search volume, competition, or commercial-intent data. A word/phrase repeated on the page might not be a phrase anyone actually searches for. Genuine keyword strategy requires a tool like Google Keyword Planner, Ahrefs, or SEMrush (see “Not Assessed” below).
Potential impact if fixed: Aligning the title, H1, and opening paragraph around one clear topic can support relevance for that phrase — but confirm with real keyword research first that it's a phrase worth targeting.
Recommended fix: If “explore service” is genuinely a phrase customers search for, try working it naturally into the title, and H1 heading, and opening paragraph. Don't force it in awkwardly — it should still read naturally to a visitor.
Readability score: 47/100 -- Fairly difficult (some visitors may find this dense) (average 14 words/sentence, 1.72 syllables/word). This can happen even with short sentences (14 words/sentence here) if the vocabulary itself is technical or industry-specific (average 1.72 syllables/word) -- the formula can't distinguish appropriate industry terminology from genuinely complex writing.
Why it matters: Visitors (and search engines) favour content that's easy to scan and understand. Long, dense sentences increase bounce rate.
Potential impact if fixed: Simpler, shorter sentences tend to keep visitors reading longer and can reduce bounce rate.
Recommended fix: Try shortening some sentences (the average here is 14 words) and swapping in simpler everyday words where possible, so the content is easier for visitors to skim and understand. If the vocabulary is mostly necessary industry/technical terms for this audience, a lower score here may not reflect a real problem -- use human editorial judgment over the raw number.
Found 1 email address(es) in plain text (e.g. info@example.com.au) -- spam bots scrape these. Note: this is primarily an anti-spam/inbox-hygiene consideration, not an SEO ranking factor -- a visible, easy-to-find contact email can also support visitor trust, so this isn't automatically something to remove.
Why it matters: Email addresses shown as plain, clickable text are routinely scraped by spam bots that crawl the web looking for exactly this.
Potential impact if fixed: Switching to a contact form (or obfuscating the address) can meaningfully cut down on spam email.
Recommended fix: Keep the visible email address if it's useful for visitors and spam hasn't become a real problem. If unwanted spam does become an issue, consider a contact form or spam filtering instead of hiding contact information visitors may actually want.
No links to social media profiles found on the page.
Why it matters: Links to active social profiles help build trust with visitors and give search engines additional signals about the business's legitimacy and online presence.
Potential impact if fixed: Adding social links is a quick trust-builder and can drive additional traffic from social platforms.
Recommended fix: If the business has active social media accounts, add links to them (often in the header or footer) so visitors can find and follow them.
6 HTTPS page(s) checked don't send a Strict-Transport-Security header.
Why it matters: HSTS tells browsers to always use HTTPS for this site, even if a visitor types or clicks an http:// link, closing a small window where an attacker could intercept that first insecure request.
Potential impact if fixed: Adding this header is a one-time server configuration change that strengthens HTTPS for every visitor.
Recommended fix: Ask your web host or developer to add the Strict-Transport-Security header at the server level (most hosts and CDNs, e.g. Cloudflare, have a simple toggle for this).
No /llms.txt file was found.
Why it matters: llms.txt is an emerging, informal convention some sites use to guide AI/LLM crawlers (e.g. for AI search tools) similar in spirit to robots.txt. It is not yet a formal or required web standard.
Potential impact if fixed: Adding one is optional and low-priority, but may become more relevant as AI-powered search grows.
Recommended fix: This is optional and not required today. If you want to add one, it's a simple text file at the site root describing the site for AI crawlers -- low priority compared to everything else in this report.
2 page(s) have under 250 words. IMPORTANT CAVEAT: word count alone does NOT reliably indicate thin or low-quality content. A gallery, portfolio, or product-grid page can fully satisfy what a visitor searched for with very little text. Treat this as a prompt to manually check each page against real search intent — not as a confirmed problem.
Why it matters: Google's own guidance evaluates whether a page satisfies search intent, not word count. This automated check can only measure the latter, which is a weak proxy at best.
Potential impact if fixed: Where a flagged page genuinely doesn't serve visitor intent well, adding genuinely useful content can help. Where it's a legitimately visual page (e.g. a gallery), no change is likely needed — verify with human judgment before acting on this.
Recommended fix: Open each page listed below and ask: would a visitor searching for this topic be satisfied with what's here? If yes (e.g. it's a photo gallery), leave it as is. If not, add more genuinely useful written content.
| Page | Word Count |
|---|---|
| https://www.example.com.au/contact.html | 131 words |
| https://www.example.com.au/quote.html | 189 words |
Mobile PageSpeed score: 68/100.
Why it matters: Google measures site speed directly and uses it as a ranking factor, especially on mobile. Slow-loading pages also lose visitors before the content even appears — studies commonly cite higher bounce rates for each extra second of load time.
Potential impact if fixed: Improving load time can reduce bounce rate, keep more visitors on the page long enough to convert, and supports better mobile search rankings.
Recommended fix: This usually needs a developer: common fixes include compressing images, removing unused code/plugins, enabling caching, and using a faster hosting plan or CDN. See the specific opportunities below for what's actually slowing this page down.
| Core Web Vital | Result |
|---|---|
| Largest Contentful Paint (main content load time) | 9.7 s |
| Cumulative Layout Shift (visual stability) | 0 |
| Total Blocking Time (responsiveness) | 0 ms |
Site is served over HTTPS.
Visitors see a secure connection with no browser warnings, and the site gets the ranking benefit Google gives to HTTPS sites.
Exactly one <h1> tag found.
The page has exactly one clear H1, giving both visitors and search engines an unambiguous main topic.
Mobile viewport meta tag present.
The page is set up to display properly on phones and tablets, where most visitors browse from.
No mixed content found -- all resources load securely.
Every resource on the page loads securely — nothing triggers a mixed-content warning.
Title tag OK (43 chars): "Example Business | Sydney"
The title is a reasonable length for both search results and browser tabs. This does not confirm it targets the best commercial search phrase for the business — that requires keyword research (see “Not Assessed”).
All 3 images have alt text.
Every image has alt text, supporting both accessibility and search engines' understanding of the page.
Missing pages correctly return a 404 status.
Missing pages correctly return a 404 status, so search engines know not to index them.
Compression is enabled (br).
Compression is enabled, so pages transfer faster to every visitor.
Found 5 of 5 basic trust-signal indicators on the homepage: an About/company-info page linked, a Contact page linked, mentions of who runs the business or its history, reviews or testimonials referenced, a recognizable physical address. This is a coarse presence check only, not a genuine E-E-A-T assessment.
Several basic trust-signal indicators were found. This does not confirm strong E-E-A-T — it only confirms these specific signals are present. A genuine E-E-A-T review needs a human to assess content quality, expertise, and authenticity.
All known AI training and search/retrieval bots are allowed to crawl this site.
AI search and retrieval bots can crawl the site, keeping it eligible for citation in AI-generated answers.
| Bot | Category | Purpose | Status |
|---|---|---|---|
| GPTBot | Training | OpenAI — trains OpenAI's models | Allowed |
| ClaudeBot | Training | Anthropic — trains Claude models | Allowed |
| Google-Extended | Training | Google — controls use in Gemini/AI Overviews training (token only, no separate crawler) | Allowed |
| Applebot-Extended | Training | Apple — controls use in Apple Intelligence training (token only) | Allowed |
| CCBot | Training | Common Crawl — a dataset used to train many AI models | Allowed |
| Bytespider | Training | ByteDance — trains ByteDance's AI models | Allowed |
| Meta-ExternalAgent | Training | Meta — trains Meta AI models | Allowed |
| Amazonbot | Training | Amazon — used for Alexa/AI systems | Allowed |
| OAI-SearchBot | Live Search & Citations | OpenAI — powers ChatGPT Search citations | Allowed |
| ChatGPT-User | Live Search & Citations | OpenAI — live fetch when a ChatGPT user asks about this page | Allowed |
| Claude-SearchBot | Live Search & Citations | Anthropic — indexes pages for Claude's search and citations | Allowed |
| Claude-User | Live Search & Citations | Anthropic — live fetch when a Claude user references this page | Allowed |
| PerplexityBot | Live Search & Citations | Perplexity — indexes pages for cited answers | Allowed |
| Perplexity-User | Live Search & Citations | Perplexity — live fetch when a Perplexity user asks about this page | Allowed |
Note: robots.txt is a voluntary, honor-system standard. Reputable AI companies generally respect it, but it isn't a technical guarantee against every bot.
Meta description OK (117 chars).
Search visitors see a well-sized, relevant summary instead of Google guessing one from the page content.
Heading levels are used in a logical order.
Headings are nested in a logical order, which helps both accessibility tools and search engines parse the page's structure.
Text-to-HTML ratio is 36.6% -- reasonable.
There's a healthy amount of visible text relative to the underlying code.
URLs use hyphens (or no separators) rather than underscores.
URLs are clean and use hyphens rather than underscores, making them easy to read.
robots.txt found at https://www.example.com.au/robots.txt with no Disallow rules (everything is crawlable). Declares 1 sitemap(s): https://www.example.com.au/sitemap.xml.
robots.txt exists. See below for the actual rules it contains — confirming it exists doesn't confirm it's configured correctly.
sitemap.xml found at https://www.example.com.au/sitemap.xml. See “XML Sitemap Coverage” below for how many URLs it actually lists.
A sitemap is in place. See below for how many URLs it actually lists.
A matching Google Business Profile was found for this business.
Keeping the business name, address, and phone number identical across the website, this Google listing, and any online directories (NAP consistency) is a well-known local search ranking factor.
Matched listing: Example Business • No ratings yet
Listed address: 123 Sample Street, Sydney NSW 2000
Google categories: car repair
Opening hours (as listed on Google):
Not covered by this check (requires ongoing rank-tracking, not a one-off API lookup): local pack ranking position, review velocity over time, photo count/quality, and competitor comparison. See “Not Assessed” below.
No broken links found among the pages crawled.
Visitors and search engines can follow every link on the site without hitting a dead end.
All 6 crawled page(s) have a meta description.
Every page has its own summary to control how it's pitched in search results, rather than leaving it to search engines to generate one automatically.
No broken images found among the pages crawled.
Every image on the site loads correctly instead of showing a blank box.
No links with empty anchor text found among the pages crawled.
Every link has descriptive text or a label, helping both screen reader users and search engines.
No redirect chains found among crawled internal links.
Internal links point straight to their final destination with no unnecessary hops.
Directly checked all 5 URLs listed in the sitemap: 5 indexable, 0 redirected, 0 noindexed, 0 broken, 0 real orphaned content page(s), 0 orphaned system page(s).
Every sitemap URL was checked directly and resolves correctly, with no unexplained orphaned content pages.
Only one phone number found across the site.
A consistent phone number across every page supports local search rankings and avoids confusing customers.
The sitemap lists 5 URL(s). This scan crawled 6 page(s) via internal links (no page cap applied), and separately fetched every one of the 5 sitemap URLs directly — see “Full URL Inventory & Indexability” above for the live status of every single one.
Confirms the sitemap is a real, parseable list of page URLs, and that its full contents (not just internally-linked pages) were checked directly.
Desktop PageSpeed score: 93/100.
Fast load times keep visitors on the page and support better mobile search rankings.
| Core Web Vital | Result |
|---|---|
| Largest Contentful Paint (main content load time) | 1.7 s |
| Cumulative Layout Shift (visual stability) | 0.041 |
| Total Blocking Time (responsiveness) | 0 ms |
Checked 13 keyword(s) — 5 rank in the top 10, 2 in the top 3.
| Keyword | Position | Ranking URL |
|---|---|---|
| example business services | 4 | http://www.example.com.au/ |
| trusted local services | Not in Top 100 | — |
| get quote | Not in Top 100 | — |
| family owned operated | Not in Top 100 | — |
| serving the local area | Not in Top 100 | — |
| trusted local provider | 2 | http://www.example.com.au/ |
| example business services for sale | 2 | http://www.example.com.au/ |
| example business services near me | 4 | http://www.example.com.au/ |
| example business services Sydney | 4 | http://www.example.com.au/ |
| trusted local services for sale | Not in Top 100 | — |
| trusted local services near me | Not in Top 100 | — |
| trusted local services Sydney | Not in Top 100 | — |
| get quote for sale | Not in Top 100 | — |
An AI Overview appeared for 6 of the 13 keyword(s) checked — this site was cited as a source in 1 of them.
| Keyword | Your Site | Domains Cited Instead |
|---|---|---|
| get quote | Not cited | aami.com.au, allianz.com.au, budgetdirect.com.au, bupa.com.au, comparethemarket.com.au |
| family owned operated | Not cited | 7eleven.com.au, abc.net.au, bellpotter.com.au, en.wikipedia.org, facebook.com |
| serving the local area | Not cited | example-reference.org, nine.com.au, police.nsw.gov.au, sevenhills-h.schools.nsw.gov.au, sevenhillsfamilydoctors.com.au |
| trusted local provider | Cited | example.com.au, facebook.com |
| trusted local services Sydney | Not cited | — |
| get quote for sale | Not cited | carsales.com.au, easyauto123.com.au |
Rather than silently leaving these out, here is exactly what this scan does not cover, why, and how to get each one done properly.
Why it wasn't assessed: SecureNow doesn't have access to a backlink index. Discovering referring domains, link authority, anchor text distribution, or toxic/spam links requires a crawled web-scale link graph.
How to get this done:
Why it wasn't assessed: The “Focus Keyword Usage” check earlier in this report only guesses a likely topic phrase from on-page text frequency — it has no access to how many people actually search for any term, how competitive it is, or its commercial intent.
How to get this done:
Why it wasn't assessed: Comparing this site's rankings, content, or backlink profile against competitors requires querying live search results and competitor data at scale, which SecureNow does not do.
How to get this done:
Why it wasn't assessed: This is the single most important gap in any automated scan like this one. Without authenticated access to the site's own Google Search Console property, there is no way to know actual ranking keywords, impressions, click-through rate, real indexing status, or manual actions.
How to get this done:
Why it wasn't assessed: Beyond basic duplicate-title/description and word-count checks, judging whether content demonstrates topical authority, covers the right subjects, or competes against itself (cannibalization) requires either expert manual review or a content-gap tool cross-referenced with real keyword data.
How to get this done:
This report covers on-page technical SEO fundamentals plus a site-wide crawl. It is not a guarantee of specific rankings or traffic — search engines weigh many other factors (content quality, backlinks, competition) — but each item above reflects a widely recognized best practice. See "Not Assessed" above for what this report deliberately does not claim to cover.
Findings and recommendations reflect your website's status at the time of the audit and are based on publicly available search engine guidelines and current best practice. Search rankings are set by Google, Bing and other providers' own algorithms, which SecureNow does not control, influence or guarantee — actual ranking positions, traffic changes and timeframes for results may vary and are not guaranteed.