Your position
47th percentile of 36 sites audited. The average site scores 73, the median 74.
Website audit report
scenegenerator.io
73
/ 100
C · Needs work
1 critical and 8 high-severity issues found across 131 checks.
- Checks run
- 131
- Passed
- 84
- Failed
- 37
- Pages crawled
- 12
Scanned 2026-09-25T03:33:17+00:00 · 4 host IPs · cert expires in 36 days
This report is not offered to search engines. It is reachable by link only. If you own scenegenerator.io you can publish or delete it.
How you compare
Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.
Sites built like yours
75 is the average for the 5 sites we have audited on custom / Cloudflare / Cloudflare, and you are below it.
The most unusual thing you fail
Exactly one SPF record
97% of the sites we have audited get this right and yours does not. Of everything on this report, it is the fault that most sets you apart from your competition, which makes it the first thing worth fixing.
Inbox Trust Index
Our own measure of whether your domain is trusted by the systems that decide if mail reaches an inbox. No other website audit reports this. It is built from BounceZero's deliverability platform.
12
/ 100
Critical
Your domain fails the basic checks receivers run before they trust a message.
What is pulling it down: SPF record · DMARC enforcement · DKIM signing. See the email deliverability section below.
Measured against our corpus
We have measured deliverability across 250,502 domains. Yours is not among them, which simply means no one has needed to verify an address at it. The score above is from live measurements of your own DNS.
For context, 4.3% of the domains we have measured accept mail to any address, which makes their bounce behaviour unpredictable.
How your page actually renders
Loaded in a real browser at phone size. This is close to what a visitor and Google's renderer see.
- Largest paint
- 1.3s
- Layout shift
- 0
- Requests
- 61
- Words rendered
- 1448
- JS errors
- 0
- Failed resources
- 0
Your plan
The 37 faults on this report come from 14 underlying causes. Fixing a cause fixes everything under it, so this is ordered by score returned per unit of work, not by severity alone.
The 6 quickest steps here take you from 73 to about 84. That is 11 points for changes measured in minutes and hours, not weeks.
1. Fix email authentication
DNS edit · minutes→ 79/100These are all records in your DNS. One editing session fixes every one of them, and it is the change most likely to stop your mail being filtered.
Fixes 6 findings: Exactly one SPF record · DMARC policy is enforced · DKIM signing is configured · MTA-STS policy published · TLS reporting enabled · BIMI logo published
2. Make the structured data qualify
Template change · a few hours→ 84/100Rich results — ratings, prices, FAQs, breadcrumbs — are what turn a listing into an advert, and they are decided by whether a few required properties are present. Markup that is invalid or incomplete is work already done that currently earns nothing.
Fixes 6 findings: The business is a describable entity · Content is marked up to be answered · The business is identified in structured data · Breadcrumbs are marked up · Site-wide search is declared · The entity links out to its profiles
3. Complete the security headers
Server or CDN config · under an hour→ 87/100All set in the same place — your web server or CDN. Half of them are single lines.
Fixes 6 findings: HTTP redirects to HTTPS · HSTS header · Content Security Policy header · MIME sniffing protection header · Clickjacking protection header · Referrer policy header
4. Close the takeover and impersonation gaps
DNS edit · minutes→ 88/100A subdomain pointing at a service that released it can be claimed by anyone, who then publishes on your domain. Deleting the record costs nothing and closes it immediately.
Fixes 1 finding: No lookalike domain can send mail as your brand
5. Point the site's own authority at the pages that earn
Template change · a few hours→ 91/100Internal links decide which of your pages search engines treat as important, and the decision is usually an accident of navigation design. It costs nothing to change and it changes what ranks.
Fixes 3 findings: Every page is linked from somewhere · Every page is linked from another · Each page covers a distinct subject
6. Remaining individual fixes
Mixed · varies→ 93/100These do not share a root cause with anything else on the report.
Fixes 3 findings: Pages carry more than their template · Pages deliver what their titles promise · The writing is readable
7. Show who stands behind the content
Content work · days→ 95/100Google's guidance asks who produced a page and why they should be trusted. For advice, health, legal or financial topics an anonymous, undated page competes badly against a named one.
Fixes 3 findings: Content identifies who wrote it · There is a route to who you are · A publisher is declared in structured data
8. Write the titles and descriptions
Content work · days→ 97/100Your title and description are the advert Google runs for you, free, every time someone searches.
Fixes 2 findings: Page titles are unique · Meta descriptions are unique
9. Fix the page on a phone
Template change · a few hours→ 98/100Google indexes the mobile version of your site, and these are measured in a real phone-sized browser rather than inferred. A page that scrolls sideways or needs pinching to read loses the visitor before the content matters.
Fixes 1 finding: Tap targets are big enough to hit
10. Make the sitemap trustworthy
Server or CDN config · under an hour→ 98/100lastmod is how Google decides what to recrawl first. A timestamp that is identical on every URL is a build date, and Google learns to ignore lastmod for the whole site once it notices.
Fixes 1 finding: Sitemap lastmod dates are meaningful
11. Harden DNS and hosting
Server or CDN config · under an hour→ 98/100Resilience and reputation work — lower urgency, but cheap while you are already in these systems.
Fixes 2 findings: DNSSEC enabled · CAA record restricts certificate issuance
12. Decide whether AI assistants may cite you
Server or CDN config · under an hour→ 99/100A growing share of questions are answered without a results page. Being quotable is a distribution channel, and it is usually blocked by a plugin default rather than a decision.
Fixes 1 finding: A curated summary is published for assistants
13. Reduce what the page has to load
Development work · days to weeks→ 99/100Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.
Fixes 1 finding: Images declare width and height
14. Serve images at the right size and format
Development work · days to weeks→ 100/100Images are what Largest Contentful Paint usually measures, and WebP is typically a third smaller than the same JPEG. On image-led pages this is the largest saving available.
Fixes 1 finding: Images are sized for the device
Fix these first
Ranked by severity, then by how much score each returns.
- critical
1. Exactly one SPF record
+14 pts2 SPF records are published. RFC 7208 allows exactly one — a receiver that sees two returns PermError and treats SPF as failed rather than merging them. Every message you send is currently failing SPF at Gmail, Outlook and Yahoo.
v=spf1 include:_spf.mx.cloudflare.net ~all v=spf1 include:_spf.google.com ~all
How to fix: Delete both records and publish one merged record containing every sending service, ending in ~all.
Reference: RFC 7208 §4.5
- high
2. DMARC policy is enforced
+9 ptsNo DMARC record. You have neither protection against domain spoofing nor any visibility into it.
How to fix: Publish v=DMARC1; p=none; rua=mailto:dmarc@yourdomain to start, then tighten to quarantine.
- high
3. DKIM signing is configured
+8 ptsNo DKIM keys found on any common selector. Without DKIM your mail cannot prove it was not altered in transit, and DMARC cannot pass on forwarded messages.
How to fix: Enable DKIM in your mail provider and publish the key it gives you.
- high
4. No lookalike domain can send mail as your brand
+8 ptsWe generated and checked 60 plausible misspellings and variants of your domain. 1 of the 1 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.
scenegenerator.com [mail configured]
How to fix: Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.
- high
5. Page titles are unique
+6 pts2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one. Every page of this type that was checked has this fault, and your sitemap lists 22 pages built from the same template (/templates/{slug}) — so this is most likely one template fix affecting up to 22 pages, not 1.
2× Editorial cover design template | SceneGenerator
2 affected URLs
How to fix: Give every page a title describing that page specifically.
Full results
Security & trust
Whether the connection, certificate and headers hold up.
4 passed · 6 failed
63%
- ✕HTTP redirects to HTTPShigh
http:// does not redirect to https://, so the insecure version of every page stays reachable and can be indexed as duplicate content.
Add a permanent 301 redirect from http:// to https://.
- ✕HSTS headermedium
Missing. Tells browsers to only ever connect over HTTPS.
Send Strict-Transport-Security: max-age=31536000; includeSubDomains
- ✕Content Security Policy headermedium
Missing. Limits where scripts may load from, which is the main defence against injected code and card skimmers.
Add a Content-Security-Policy header, starting in report-only mode.
- ✕MIME sniffing protection headerlow
Missing. Stops browsers guessing file types.
Send X-Content-Type-Options: nosniff
- ✕Clickjacking protection headerlow
Missing. Stops your site being framed inside someone else's.
Send X-Frame-Options: SAMEORIGIN, or use CSP frame-ancestors.
- ✕Referrer policy headerlow
Missing. Controls how much of your URL is leaked to other sites.
Send Referrer-Policy: strict-origin-when-cross-origin
- ✓Served over HTTPS
Secure connection working.
- ✓No insecure mixed content
All resources load securely.
- ✓Certificate is not near expiry
Certificate valid for another 36 days (expires 2026-10-31).
- ✓Modern TLS version
Negotiated TLSv1.3.
Email deliverability
Whether your mail reaches inboxes or spam folders.
1 passed · 6 failed
12%
- ✕Exactly one SPF recordcritical
2 SPF records are published. RFC 7208 allows exactly one — a receiver that sees two returns PermError and treats SPF as failed rather than merging them. Every message you send is currently failing SPF at Gmail, Outlook and Yahoo.
v=spf1 include:_spf.mx.cloudflare.net ~all v=spf1 include:_spf.google.com ~all
Delete both records and publish one merged record containing every sending service, ending in ~all.
- ✕DMARC policy is enforcedhigh
No DMARC record. You have neither protection against domain spoofing nor any visibility into it.
Publish v=DMARC1; p=none; rua=mailto:dmarc@yourdomain to start, then tighten to quarantine.
- ✕DKIM signing is configuredhigh
No DKIM keys found on any common selector. Without DKIM your mail cannot prove it was not altered in transit, and DMARC cannot pass on forwarded messages.
Enable DKIM in your mail provider and publish the key it gives you.
- ✕MTA-STS policy publishedlow
No MTA-STS policy, so mail to you can be delivered unencrypted if an attacker strips TLS.
Publish an MTA-STS policy and the _mta-sts TXT record.
- ✕TLS reporting enabledlow
No TLS-RPT record, so delivery-encryption failures go unreported.
Publish a _smtp._tls TXT record with a reporting address.
- ✕BIMI logo publishedlow
No BIMI record. With DMARC at enforcement you could display your logo next to your messages in Gmail and Apple Mail.
Once DMARC is at quarantine or reject, publish a BIMI record with an SVG logo.
- ✓Domain can receive email
3 mail server(s) configured.
Speed & Core Web Vitals
How fast real visitors experience the site.
7 passed · 2 failed · 1 skipped
82%
- ✕Images declare width and heightmedium
7 of 41 images declare dimensions. Images without dimensions cause the page to jump as they load, which is what Cumulative Layout Shift measures.
Set width and height attributes on every image.
- ✕Images are sized for the devicelow
0 of 118 image(s) provide a srcset. Without one, a phone downloads the full desktop image and then scales it down — paying for pixels it never shows.
Add srcset and sizes so each device downloads an appropriate image.
- –Core Web Vitals from real users
Not available: PageSpeed API returned 429. This usually means the site does not yet have enough Chrome traffic for Google to report field data. Lab measurements below still apply.
- ✓Compression enabled
Served with gzip compression.
- ✓Server responds quickly
Median response across 12 page(s) was 60 ms.
- ✓Homepage HTML is not oversized
Homepage HTML is 82 KB.
- ✓Reasonable number of scripts
1 external script file(s) on the homepage.
- ✓Browser caching is allowed
Pages may be cached by browsers and CDNs.
- ✓Images use a modern format
90 image(s) are served as WebP or AVIF.
- ✓Images load lazily
35 of 41 images use lazy loading.
Search fundamentals
The tags, files and signals search engines read first.
32 passed · 7 failed · 2 skipped
86%
- ✕The business is a describable entityhigh
No Organization or Person markup. An assistant that cannot name the entity behind the site will describe the business from fragments, or not at all, which is how a competitor becomes the answer.
Add Organization JSON-LD with name, url, logo and sameAs links, so the description an assistant gives of the business is the one you wrote.
- ✕Content is marked up to be answeredhigh
No FAQPage, HowTo or QAPage markup. When an assistant answers a question about this service, the page has nothing structured to be cited from, so the citation goes to whoever wrote the answer block.
Add FAQPage schema for the questions the page answers (the answer must appear as visible text, not only in the markup) and HowTo for process content.
- ✕The business is identified in structured datamedium
No Organization markup. This is what Google assembles a knowledge panel from — the box with your logo, name and links that appears beside branded searches — and what connects your site to your social profiles. Without it Google infers your identity from third parties instead of from you.
Add Organization JSON-LD with name, url, logo and sameAs links to your social profiles.
- ✕Breadcrumbs are marked upmedium
No BreadcrumbList markup. Google replaces the raw URL in your listing with a readable breadcrumb trail when this is present, which is more legible and measurably more clickable — and it is one of the cheapest rich results to earn.
Add BreadcrumbList JSON-LD to every page below the homepage.
- ✕The entity links out to its profileslow
No entity markup to attach profiles to.
Add sameAs URLs to the Google Business Profile, LinkedIn, X and any other profiles the business owns.
- ✕Site-wide search is declaredlow
No WebSite markup. With a SearchAction it can give you a search box directly inside your Google listing for branded queries.
Add WebSite JSON-LD, with potentialAction/SearchAction if the site has its own search.
- ✕A curated summary is published for assistantslow
No /llms.txt. It is a short, plain-text map of what a site is and which pages matter — a convention some assistants read to decide what to quote, and cheap to publish. It is not yet a standard anyone is obliged to honour, so treat it as a low-cost bet rather than a requirement.
Publish /llms.txt: a heading, one paragraph describing the business, and a linked list of your most important pages.
- –Search Console connected
Not measured — not configured on this instance. Connecting Search Console adds what no crawl can see: the queries this site already appears for, where it ranks, and how many people click. It is read-only and can be disconnected at any time.
- –Current search visibility
Not measured — ranking data is not configured on this instance.
- ✓Homepage is indexable
Homepage is open to indexing.
- ✓Mobile viewport declared
Mobile viewport is declared.
- ✓Homepage title is present and well sized
Title is 43 characters.
- ✓XML sitemap published
Sitemap found listing 686 URLs.
- ✓Homepage meta description is present
Description is 151 characters.
- ✓Homepage canonical is correct
Canonical points at this page.
- ✓Structured data present
Structured data found: WebApplication.
- ✓robots.txt does not block the site
robots.txt present and open to search engines.
- ✓Canonicals point at indexable pages
Every canonical points at a page that is allowed to be indexed.
- ✓Language links point both ways
Every hreflang reference is reciprocated by the page it names.
- ✓Canonical targets are live pages
Canonical targets all return 200.
- ✓Sitemap and page directives agree
No page is both listed in the sitemap and marked noindex.
- ✓Structured data parses
All structured data blocks are valid JSON.
- ✓Noindex directives are readable
No page relies on a directive Google is blocked from reading.
- ✓Language codes are valid
Every hreflang value is a valid language or language-region code.
- ✓Marked-up content qualifies for rich results
Every marked-up entity carries the properties Google requires.
- ✓Most crawled pages are indexable
11 of 11 crawled page(s) (100%) can actually be indexed.
- ✓Each page lists itself
Every page with hreflang annotations includes itself.
- ✓Language links point at indexable pages
Every hreflang target is a live, indexable page.
- ✓No canonical chains
No canonical points at a page that then canonicals somewhere else.
- ✓Sitemap lists canonical pages only
Every sitemap URL is its own canonical.
- ✓Structured data is in the served HTML
All structured data is present in the HTML the server sends.
- ✓AI assistants can cite this site
Every major assistant is allowed to read and cite these pages.
- ✓Pages are close to the homepage
Every crawled page sits within four levels of the homepage (deepest: 3).
- ✓Social preview configured
9 Open Graph tags found.
- ✓A default version is declared
An x-default version is declared for visitors whose language matches none of your versions.
- ✓URLs are readable
URLs use lowercase, hyphenated, extension-free paths.
- ✓Content is not served behind query parameters
0 of 12 crawled URLs carry query parameters other than tracking tags.
- ✓Page language declared
Language attribute present.
- ✓Link previews are configured for X/Twitter
4 twitter: tag(s) found.
- ✓Structured data in use
12 structured data object(s) across 12 page(s): WebApplication.
- ✓Model-training access is stated
No model-training crawler is blocked, so this content may be used to train future models. This is a business decision rather than an SEO one, and it is separate from being cited in answers: refusing training does not remove you from AI results, and allowing it does not put you in them.
Content & structure
Whether pages are unique, linked and crawlable.
17 passed · 11 failed · 1 skipped
54%
- ✕Page titles are uniquehigh
2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one. Every page of this type that was checked has this fault, and your sitemap lists 22 pages built from the same template (/templates/{slug}) — so this is most likely one template fix affecting up to 22 pages, not 1.
2× Editorial cover design template | SceneGenerator
2 affected URLs
Give every page a title describing that page specifically.
- ✕Every page is linked from somewherehigh
10 of 11 crawled pages had no internal link pointing at them. Search engines discover pages by following links, so an unlinked page is found late or not at all — and passes on none of its authority. This affects every checked page of 10 templates (/de/templates/{slug}, /es/templates/{slug}, /fr/templates/{slug}), covering up to 196 pages in your sitemap. Fixing the templates fixes all of them at once.
10 affected URLs
- https://scenegenerator.io/ar/prompts/editorial-cover
- https://scenegenerator.io/ar/styles/pastel-isometric
- https://scenegenerator.io/de/prompts/editorial-cover
- https://scenegenerator.io/de/styles/pastel-isometric
- https://scenegenerator.io/de/templates/editorial-cover
- https://scenegenerator.io/es/templates/editorial-cover
- https://scenegenerator.io/fr/templates/editorial-cover
- https://scenegenerator.io/ja/templates/editorial-cover
- https://scenegenerator.io/templates/editorial-cover
- https://scenegenerator.io/zh/templates/editorial-cover
Link these from a relevant parent page, your navigation, or a hub page.
- ✕Pages carry more than their templatemedium
Across 9 page(s), the median page is 86% its own content and the rest navigation, footer and legal text. 3 page(s) carry under 120 words of their own, or less than a third. A word count that includes the template hides this — those pages look substantial and read as empty, which is what a search engine comparing them to a competitor sees. This affects every checked page of 3 templates (/ja/templates/{slug}, /zh/templates/{slug}, /de/prompts/{slug}), covering up to 60 pages in your sitemap. Fixing the templates fixes all of them at once.
12 own / 26 total (46%) https://scenegenerator.io/ja/templates/editorial-cover 14 own / 29 total (48%) https://scenegenerator.io/zh/templates/editorial-cover 117 own / 141 total (83%) https://scenegenerator.io/de/prompts/editorial-cover 168 own / 200 total (84%) https://scenegenerator.io/templates/editorial-cover 145 own / 169 total (86%) https://scenegenerator.io/de/styles/pastel-isometric 153 own / 178 total (86%) https://scenegenerator.io/de/templates/editorial-cover
3 affected URLs
Add substance to the page body rather than the template — for product pages, specifics nobody else has; for category pages, an explanation of what the category is for.
- ✕Each page covers a distinct subjectmedium
1 pair(s) of pages appear to cover the same subject, judged from their titles and headings. Two pages competing for one query split the links and relevance that should accumulate on one, and Google alternates between them — so neither settles into a stable position. Confirm against Search Console, which shows exactly which page it chooses. Every page of this type that was checked has this fault, and your sitemap lists 22 pages built from the same template (/templates/{slug}) — so this is most likely one template fix affecting up to 22 pages, not 1.
Editorial cover design template | SceneGenerator https://scenegenerator.io/templates/editorial-cover https://scenegenerator.io/templates/editorial-cover
1 affected URL
Decide which page owns the subject. Merge the weaker one into it and redirect, or narrow each to a genuinely different question.
- ✕Pages deliver what their titles promisemedium
2 page(s) have a title and heading whose subject barely appears in the body. Either the title is written for a query the page does not answer — which loses the visitor on arrival and is measurable as a bounce — or the page is about something its title does not say. This affects every checked page of 2 templates (/de/templates/{slug}, /de/prompts/{slug}), covering up to 38 pages in your sitemap. Fixing the templates fixes all of them at once.
25% of the title's subject in the body Redaktionelles Cover Designvorlage | SceneGenerator https://scenegenerator.io/de/templates/editorial-cover 25% of the title's subject in the body Redaktionelles Cover AI-Bildaufforderung | SceneGenerator https://scenegenerator.io/de/prompts/editorial-cover
2 affected URLs
Make the opening paragraph answer the title directly, or change the title to what the page is really about.
- ✕Meta descriptions are uniquemedium
4 pages share 2 duplicated meta description(s). A description is the advert for that specific page; repeating one across a site means Google usually discards it and writes its own from the page text, so you lose control of what searchers read before deciding whether to click. This affects every checked page of 3 templates (/de/templates/{slug}, /templates/{slug}, /de/prompts/{slug}), covering up to 60 pages in your sitemap. Fixing the templates fixes all of them at once.
An architecture magazine cover with exactly one sculptural cobalt chair in a quiet concret… used on 2 pages Ein Architekturmagazin-Cover mit genau einem skulpturalen Kobaltstuhl in einer ruhigen Bet… used on 2 pages
4 affected URLs
Write one description per page, describing what is on that page.
- ✕Content identifies who wrote itmedium
No author is named anywhere — no byline, no author metadata and no author in your structured data. Google's guidance on helpful content asks who produced it and why anyone should trust them, and for advice, health, legal or financial pages an anonymous page competes badly against one with a named, credentialed author.
Add a byline with a real name linking to an author page, and an author property in your Article or Organization markup.
- ✕Every page is linked from anothermedium
10 crawled page(s) are not linked from any other page we fetched. A page reachable only from a sitemap receives no internal authority at all, and is crawled rarely — it can rank, but it starts from nothing and stays there. This affects every checked page of 10 templates (/es/templates/{slug}, /ja/templates/{slug}, /zh/templates/{slug}), covering up to 196 pages in your sitemap. Fixing the templates fixes all of them at once.
scenegenerator.io/de/styles/pastel-isometric scenegenerator.io/es/templates/editorial-cover scenegenerator.io/ar/prompts/editorial-cover scenegenerator.io/ja/templates/editorial-cover scenegenerator.io/zh/templates/editorial-cover scenegenerator.io/fr/templates/editorial-cover
10 affected URLs
- https://scenegenerator.io/de/styles/pastel-isometric
- https://scenegenerator.io/es/templates/editorial-cover
- https://scenegenerator.io/ar/prompts/editorial-cover
- https://scenegenerator.io/ja/templates/editorial-cover
- https://scenegenerator.io/zh/templates/editorial-cover
- https://scenegenerator.io/fr/templates/editorial-cover
- https://scenegenerator.io/ar/styles/pastel-isometric
- https://scenegenerator.io/templates/editorial-cover
- https://scenegenerator.io/de/prompts/editorial-cover
- https://scenegenerator.io/de/templates/editorial-cover
Link them from a relevant hub page or from navigation, using the subject as the link text.
- ✕There is a route to who you aremedium
No link to an about, team or contact page was found in the pages crawled. These are the pages both people and search engines use to decide whether a site belongs to a real business, and their absence is one of the strongest signals of a site that is not worth trusting.
Link an About and a Contact page from your main navigation or footer.
- ✕The writing is readablemedium
Median reading ease is 7.0 — very difficult. 5 page(s) score below 40, which is the range of academic and legal writing. That is correct for a terms page and costly on anything meant to sell, because the reader who bounces was the one who arrived.
-20.3 (very difficult) https://scenegenerator.io/de/templates/editorial-cover -18.6 (very difficult) https://scenegenerator.io/de/prompts/editorial-cover -18.6 (very difficult) https://scenegenerator.io/de/styles/pastel-isometric 7.0 (very difficult) https://scenegenerator.io/es/templates/editorial-cover 22.3 (very difficult) https://scenegenerator.io/templates/editorial-cover
Shorter sentences and plainer words in the pages that convert. Legal pages can stay as they are.
- ✕A publisher is declared in structured datalow
No publisher in your structured data. It ties each page back to the organisation that stands behind it, which is what carries trust from your brand to an individual article.
Add a publisher property naming your Organization, with its logo.
- –Content carries recent dates
Not measured — no page declares a publication or modification date, so how recently the site was maintained cannot be determined. That is normal for a brochure site and worth fixing for anything article-based.
- ✓Pages have enough content
3 of 12 crawled pages carry under 150 words. Thin pages rarely rank and can drag down how the whole site is assessed.
- ✓Every page has a meta description
0 of 12 crawled pages have no meta description.
- ✓Images have alt text
0 of 118 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.
- ✓Navigation is present on every page
Every crawled page carries at least three internal links, so navigation is consistently rendered.
- ✓Pages are meaningfully different from each other
No two crawled pages share substantially the same text.
- ✓No broken internal pages
All 12 crawled pages returned successfully.
- ✓Missing pages return a real 404
No page answers 200 while telling the visitor nothing was found.
- ✓Navigation promotes pages that earn money
0 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated.
- ✓Links describe where they go
0 of 515 internal link(s) use text like 'click here' or no text at all.
- ✓No phrase is repeated unnaturally
No phrase dominates a page's text.
- ✓One H1 per page
0 of 12 pages do not have exactly one H1 heading.
- ✓No long redirect chains
No multi-step redirects found.
- ✓Sitemap matches the real site
Sitemap lists 686 URLs; we reached 11 by crawling. 675 sitemap URLs were not linked from the pages we visited.
- ✓No dead-end pages
Every crawled page links onward.
- ✓Internal authority is spread, not pooled
Pages receive 0.0 internal links on average across the crawl, with no single page absorbing most of them.
- ✓Where internal authority goes
Internal links concentrate authority on the pages below, in order. This is the site's own ranking of itself, derived from how it links — read it against what the business actually sells, because search engines read it the same way. Only the crawled sample is modelled, so this describes the navigation rather than every page.
- ✓What each page is about
The terms that distinguish each page from the others on this site — not the most frequent words, but the ones this page uses and the others do not. Read them as what a search engine would take the page to be about, and check that it matches what it is for.
Local business signals
What Google needs to place you in map results.
0 passed · 0 failed · 1 skipped
100%
- –Local business signals
Not applicable — nothing on this site indicates a physical location customers visit: no address, phone link, opening hours, map or local business markup. Local search checks are skipped and do not affect the score. If you do serve customers from premises, publishing an address and phone number is the place to start.
Infrastructure
DNS, hosting and delivery configuration.
11 passed · 4 failed · 4 skipped
75%
- ✕No lookalike domain can send mail as your brandhigh
We generated and checked 60 plausible misspellings and variants of your domain. 1 of the 1 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.
scenegenerator.com [mail configured]
Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.
- ✕Sitemap lastmod dates are meaningfulmedium
Only 14 of 686 sitemap URL(s) declare a lastmod. It is the signal Google uses to decide what to recrawl first, so without it updates are found late.
['2026-07-24T00:00:00.000Z', '2026-07-24T00:00:00.000Z', '2026-07-24T00:00:00.000Z']
Emit lastmod from the date the page content actually changed, not from the time the sitemap was generated.
- ✕DNSSEC enabledlow
DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.
Enable DNSSEC at your DNS provider.
- ✕CAA record restricts certificate issuancelow
No CAA record, so any certificate authority may issue certificates for your domain.
Publish a CAA record naming the certificate authority you use.
- –Mail server IP is not blacklisted
Not checked: the blocklists declined queries from this resolver, so reputation could not be confirmed either way. This is excluded from your score rather than guessed at.
- –Certificate history reviewed
Not measured — the certificate transparency log was unavailable (returned 502).
- –Server log analysis
Not measured — no log file supplied. Server logs are the only source that shows what Googlebot actually fetched rather than what it could fetch: which pages it spends its crawl on, which it has never asked for, and what it receives when it does.
- –Whole-site analysis
Not measured — no whole-site crawl has been run for this domain. The audit above reasons from a sample of pages chosen to cover each template, which describes how the site is built. It cannot say how many of the site's pages are indexable, which templates are thin across every instance, or what sits too deep to be crawled — those are counts, and a sample cannot produce one.
- ✓Redundant nameservers
2 nameserver(s) configured.
- ✓No subdomain can be taken over
Checked 0 subdomain(s); none point at a cloud service that has released them.
- ✓No unbounded URL spaces
No filter, session or calendar URLs that would generate an unbounded space were found.
- ✓Pages are reached without redirect chains
Every page was reached directly or in a single hop.
- ✓Crawled URLs return content
0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).
- ✓Certificate is not shared with unrelated domains
Your certificate covers only your own domain.
- ✓Sitemap files are within Google's limits
Every sitemap file is within the 50,000 URL and 50 MB limits.
- ✓Internal links pass authority
0 internal link(s) are marked nofollow.
- ✓Software versions are not disclosed
No version numbers advertised in response headers.
- ✓Hosting network identified
Served from AS13335 (CLOUDFLARENET - Cloudflare, Inc.), announced in 104.21.48.0/20 — a block of 4,096 addresses.
- ✓What this audit examined
12 page(s) were examined, chosen to cover 11 of the 182 distinct page templates found across 686 known URLs. Pages are sampled by template rather than in sitemap order, because the first pages of a sitemap are usually all the same kind — a sample of one template would describe that template rather than the site. Findings below therefore apply to the templates listed, and a fault in a template is normally a fault on every page built from it.
Off-page authority
Who links to this site, with what text, and how that compares.
0 passed · 0 failed · 1 skipped
100%
- –Off-page profile
Not measured — off-page data is not configured on this instance.
What Google's renderer sees
The site loaded in a real browser, the way a visitor and a crawler get it.
12 passed · 1 failed
94%
- ✕Tap targets are big enough to hitmedium
44 of 77 tappable element(s) are smaller than 48x48 pixels, and 32 sit closer than 8 pixels to a neighbour. On a phone that means links and buttons that are hard to hit without zooming, and mis-taps on a checkout or contact button cost conversions directly.
SceneGenerator (166x28) Open menu (36x36) Text to image (121x32) Image to image (132x32) Nano Banana (112x36)
Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.
- ✓Content is in the HTML, not built by JavaScript
The served HTML contains 1439 words and the rendered page 1448 — the content is present before JavaScript runs.
- ✓The mobile page matches the desktop page
What the server sends a phone matches what it sends a desktop browser.
- ✓JavaScript does not rewrite indexing directives
The canonical and robots directives are the same before and after JavaScript runs.
- ✓Largest Contentful Paint under 2.5s (lab)
Measured 1.3s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.
- ✓Navigation links are crawlable without JavaScript
54 links in the served HTML, 54 after rendering — navigation is discoverable.
- ✓Layout stays stable while loading (lab)
Cumulative Layout Shift measured at 0.000 (good is 0.1 or less).
- ✓No JavaScript errors on load
The page loaded without JavaScript errors.
- ✓All page resources load successfully
Every image, script and stylesheet loaded.
- ✓The page fits the screen
The page fits the mobile viewport with no sideways scrolling.
- ✓No excessive JavaScript blocking
0 long JavaScript task(s) blocked the main thread while loading.
- ✓Body text is legible on a phone
0 of 157 text block(s) render below 12px on a mobile viewport.
- ✓Reasonable number of requests
The page made 61 network requests to load.
Scan details
| Final URL | https://scenegenerator.io/ |
|---|---|
| Host IPs | 104.21.63.148, 172.67.147.30, 2606:4700:3030::6815:3f94, 2606:4700:3034::ac43:931e |
| Pages crawled | 12 of 12 attempted |
| Sitemap URLs | 686 |
| Nameservers | adrian.ns.cloudflare.com, bruce.ns.cloudflare.com |
| Mail servers | route1.mx.cloudflare.net, route2.mx.cloudflare.net, route3.mx.cloudflare.net |
| DKIM selectors | none found |
| Mail server IPs | 162.159.205.12, 162.159.205.13, 162.159.205.11 |
| TLS | TLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by Google Trust Services |
| Detected stack | custom / Cloudflare / Cloudflare |
| Browser render | Camoufox (stealth Firefox) · 6.5s · 1448 words, 54 links after JavaScript |
12 URLs crawled
- https://scenegenerator.io/
- https://scenegenerator.io/es/templates/editorial-cover
- https://scenegenerator.io/de/templates/editorial-cover
- https://scenegenerator.io/ja/templates/editorial-cover
- https://scenegenerator.io/templates/editorial-cover
- https://scenegenerator.io/zh/templates/editorial-cover
- https://scenegenerator.io/ar/prompts/editorial-cover
- https://scenegenerator.io/ar/styles/pastel-isometric
- https://scenegenerator.io/de/prompts/editorial-cover
- https://scenegenerator.io/de/styles/pastel-isometric
- https://scenegenerator.io/fr/templates/editorial-cover
- https://scenegenerator.io/templates/editorial-cover
Want these fixed?
BounceZero Ltd does this work: technical remediation, local SEO and email deliverability. Tell us what you want fixed and we'll reply with what it takes. No call required, no obligation.
Watch this site
We re-audit on a schedule and email you only when a check that was passing starts failing. That is usually a recent change to the site or its DNS, and it is findable while still fresh. No digest, no newsletter.
Monitoring means repeatedly fetching your site and emailing about it, so we ask you to prove you own scenegenerator.io first.