Regressed: was passing, now failing
- Navigation promotes pages that earn money
Website audit report
1 critical and 3 high-severity issues found across 127 checks.
Scanned 2026-08-17T22:23:58+00:00 · 2 host IPs · cert expires in 87 days
This report is not offered to search engines. It is reachable by link only. If you own stripe.com you can publish or delete it.
A few checks regressed since the last audit. None are critical, but they were passing before. Score +1.
Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.
79th percentile of 28 sites audited. The average site scores 71, the median 67.
Reasonable number of requests
92% 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.
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.
Your domain is configured the way the top tier of senders are.
Most addresses we have tested here are deliverable. Mailbox quality at your domain ranks in the 78th percentile of domains we have verified enough addresses at to judge.
First measured 2026-07-16.
Loaded in a real browser at phone size. This is close to what a visitor and Google's renderer see.

Oldest on the left. Every re-run is kept.
The 25 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 5 quickest steps here take you from 83 to about 89. That is 6 points for changes measured in minutes and hours, not weeks.
A canonical or noindex injected at runtime silently overrides what the server said, and the served HTML still looks correct to anyone reading the source.
Fixes 1 finding: JavaScript does not rewrite indexing directives
Resilience and reputation work — lower urgency, but cheap while you are already in these systems.
Fixes 3 findings: No JavaScript errors on load · All page resources load successfully · DNSSEC enabled
These decide whether your pages can appear at all. Nothing else on this report matters until they are right.
Fixes 2 findings: No unexpected noindex pages · XML sitemap published
A 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
These 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 3 findings: MTA-STS policy published · TLS reporting enabled · BIMI logo published
Internal 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 2 findings: Navigation promotes pages that earn money · Each page covers a distinct subject
Your title and description are the advert Google runs for you, free, every time someone searches.
Fixes 3 findings: Page titles are unique · Meta descriptions are unique · One H1 per page
Google 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 2 findings: Tap targets are big enough to hit · Body text is legible on a phone
Google'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 2 findings: Content carries recent dates · A publisher is declared in structured data
Rich 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 1 finding: Breadcrumbs are marked up
Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.
Fixes 2 findings: Reasonable number of scripts · Reasonable number of requests
These do not share a root cause with anything else on the report.
Fixes 1 finding: The writing is readable
A 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
Images 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
Ranked by severity, then by how much score each returns.
JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.
canonical: served 'https://stripe.com/ie', rendered 'https://stripe.com/en-fr'
How to fix: Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.
We generated and checked 51 plausible misspellings and variants of your domain. 16 of the 29 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.
5tripe.com [mail configured] my-stripe.com [mail configured] sripe.com [mail configured] steipe.com [mail configured] stipe.com [mail configured] stirpe.com [mail configured] strie.com [mail configured] strile.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.
2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.
2× Stripe | Financial Infrastructure to Grow Your Revenue
How to fix: Give every page a title describing that page specifically.
1 of 12 crawled pages are set to noindex. If any of these are meant to bring in traffic, they currently cannot.
How to fix: Review each and remove noindex where the page should rank.
Whether the connection, certificate and headers hold up.
Secure connection working.
Plain HTTP requests are redirected to the secure version.
All resources load securely.
Certificate valid for another 87 days (expires 2026-11-12).
Negotiated TLSv1.3.
HSTS is set.
Content Security Policy is set.
MIME sniffing protection is set.
Clickjacking protection is set.
Referrer policy is set.
Whether your mail reaches inboxes or spam folders.
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.
No TLS-RPT record, so delivery-encryption failures go unreported.
Publish a _smtp._tls TXT record with a reporting address.
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.
DKIM keys published on selector(s): google, s1, s2, mandrill.
5 mail server(s) configured.
Ends in ~all (soft fail) — the usual safe setting.
The record forces about 3 DNS lookups. Comfortably within the limit of 10.
Aggregate reports are being sent to a reporting address.
One SPF record, as required.
DMARC policy is p=reject.
How fast real visitors experience the site.
75 external script file(s) on the homepage. Each one is a separate request that can block rendering.
Remove unused third-party tags and combine what remains.
73 of 545 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.
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.
Served with gzip compression.
Median response across 12 page(s) was 746 ms.
Homepage HTML is 666 KB.
30 of 31 images declare dimensions.
Pages may be cached by browsers and CDNs.
All 104 image(s) are JPEG or PNG, with no WebP or AVIF alternative. WebP is typically 25-35% smaller at the same quality and is supported by every current browser — on image-led pages this is usually the single largest saving available, and images are what Largest Contentful Paint measures.
30 of 31 images use lazy loading.
The tags, files and signals search engines read first.
No XML sitemap. Google has to discover your pages by following links, which means deeper pages may never be crawled.
0 URLs
Publish sitemap.xml and reference it from robots.txt.
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.
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.
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.
Not measured — ranking data is not configured on this instance.
Homepage is open to indexing.
Mobile viewport is declared.
Title is 54 characters.
Description is 148 characters.
Canonical points at this page.
Structured data found: ContactPoint, ImageObject, Organization, Person, Place, PostalAddress, WebSite.
robots.txt present and open to search engines.
Every canonical points at a page that is allowed to be indexed.
Every hreflang reference is reciprocated by the page it names.
Canonical targets all return 200.
All structured data blocks are valid JSON.
No page relies on a directive Google is blocked from reading.
Every hreflang value is a valid language or language-region code.
Every marked-up entity carries the properties Google requires.
10 of 11 crawled page(s) (91%) can actually be indexed.
Every page with hreflang annotations includes itself.
Every hreflang target is a live, indexable page.
Identified as Organization, Person.
No canonical points at a page that then canonicals somewhere else.
All structured data is present in the HTML the server sends.
Every major assistant is allowed to read and cite these pages.
Every crawled page sits within four levels of the homepage (deepest: 4).
5 Open Graph tags found.
An x-default version is declared for visitors whose language matches none of your versions.
URLs use lowercase, hyphenated, extension-free paths.
0 of 12 crawled URLs carry query parameters other than tracking tags.
Language attribute present.
WebSite markup is present.
5 twitter: tag(s) found.
109 structured data object(s) across 12 page(s): Article, ContactPoint, ImageObject, NewsArticle, Organization, Person, Place, PostalAddress, WebSite.
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.
Whether pages are unique, linked and crawlable.
2 pages share 1 duplicated title(s). Google treats near-identical pages as competing with each other, and usually indexes only one.
2× Stripe | Financial Infrastructure to Grow Your Revenue
Give every page a title describing that page specifically.
1 of 12 crawled pages are set to noindex. If any of these are meant to bring in traffic, they currently cannot.
Review each and remove noindex where the page should rank.
75 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated. 6 of them point at legal, account or administrative pages, and 2 of those sit among the eight best-linked pages on the site — level with, or above, the pages you sell from. Nobody decides this: a crawler counts every footer link as an endorsement repeated on every page, while visitors ignore footers. Those pages must exist and should not be among the best-linked things you publish.
stripe.com/ie/pricing 0.1% stripe.com/ie/contact/sales 0.1% stripe.com/ie/enterprise 0.1% stripe.com/ie/professional-services 0.1% stripe.com/ie/partners 0.1% stripe.com/ie/support-plans 0.1% stripe.com/ie/startups 0.1% stripe.com/ie/atlas 0.1%
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.
Stripe | Financial Infrastructure to Grow Your Revenue https://stripe.com/ie https://stripe.com/ie
Decide which page owns the subject. Merge the weaker one into it and redirect, or narrow each to a genuinely different question.
2 pages share 1 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.
Stripe is a financial services platform that helps all types of businesses accept payments… used on 2 pages
Write one description per page, describing what is on that page.
1 of 12 crawled pages declare a date; the most recent is 2023-05-03 — about 40 months ago. Nothing on the site appears to have been updated since. For most topics Google prefers a recently maintained page over an older one of equal quality, and visitors read a stale date as a sign the business may not still be active.
most recent declared date: 2023-05-03; 8% of pages carry one
Review and update the most important pages, and publish dateModified so the update is visible.
Median reading ease is 44.4 — difficult. 4 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.
31.4 (difficult) https://stripe.com/ie/support-plans 36.0 (difficult) https://stripe.com/ie/industries/public-sector 36.1 (difficult) https://stripe.com/ie/newsroom/news/stripe-and-uber 36.4 (difficult) https://stripe.com/ie/guides/introduction-to-risk-management 44.4 (difficult) https://stripe.com/ie
Shorter sentences and plainer words in the pages that convert. Legal pages can stay as they are.
12 of 12 pages do not have exactly one H1 heading.
Use a single H1 per page stating what the page is about.
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.
Across 11 page(s), the median page is 52% its own content and the rest navigation, footer and legal text.
All 11 crawled pages are reachable by internal links.
All 12 crawled pages carry substantial content.
0 of 12 crawled pages have no meta description.
8 of 545 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.
Every crawled page carries at least three internal links, so navigation is consistently rendered.
No two crawled pages share substantially the same text.
All 12 crawled pages returned successfully.
No page answers 200 while telling the visitor nothing was found.
Every page's body covers the subject its title and heading announce.
Authorship is declared.
76 of 3618 internal link(s) use text like 'click here' or no text at all.
Every crawled page is linked from at least one other page.
No phrase dominates a page's text.
An about or contact page is linked.
No multi-step redirects found.
Every crawled page links onward.
Pages receive 6.6 internal links on average across the crawl, with no single page absorbing most of them.
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.
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.
What Google needs to place you in map results.
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.
DNS, hosting and delivery configuration.
We generated and checked 51 plausible misspellings and variants of your domain. 16 of the 29 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.
5tripe.com [mail configured] my-stripe.com [mail configured] sripe.com [mail configured] steipe.com [mail configured] stipe.com [mail configured] stirpe.com [mail configured] strie.com [mail configured] strile.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.
DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.
Enable DNSSEC at your DNS provider.
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.
Not measured — the certificate transparency log was unavailable (returned 502).
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.
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.
4 nameserver(s) configured.
Checked 0 subdomain(s); none point at a cloud service that has released them.
No filter, session or calendar URLs that would generate an unbounded space were found.
Every page was reached directly or in a single hop.
0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).
Your certificate covers only your own domain.
0 internal link(s) are marked nofollow.
CAA record present.
No version numbers advertised in response headers.
Served from AS16509 (AMAZON-02 - Amazon.com, Inc.), announced in 198.137.150.0/24 — a block of 256 addresses.
12 page(s) were examined, chosen to cover 11 of the 85 distinct page templates found across 12 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.
Who links to this site, with what text, and how that compares.
Not measured — off-page data is not configured on this instance.
The site loaded in a real browser, the way a visitor and a crawler get it.
JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.
canonical: served 'https://stripe.com/ie', rendered 'https://stripe.com/en-fr'
Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.
4 JavaScript error(s) fire when the page loads. Broken scripts commonly break booking forms, menus and tracking without anything looking wrong.
[JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://b.stripecdn.com https://js.
[JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://b.stripecdn.com https://js.
[JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'”. Consider using a hash ('sh
[JavaScript Error: "Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'”. Consider using a hash ('shOpen your browser's console on the live site and fix what it reports.
166 of 185 tappable element(s) are smaller than 48x48 pixels, and 82 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.
Stripe homepage (60x25) Toggle navigation menu (40x40) Get started (358x44) Sign up with Google (358x44) A (142x34)
Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.
31 of 289 text block(s) render below 12px on a mobile viewport. Text that small forces pinch-zooming, which is the single most common reason a visitor leaves a page on a phone before reading it.
Set body text to at least 16px, and never below 12px.
The page made 110 network requests to load. Each is a round trip, and on mobile data they add up quickly.
Remove unused third-party tags, and combine or lazy-load the rest.
The served HTML contains 1915 words and the rendered page 2124 — the content is present before JavaScript runs.
What the server sends a phone matches what it sends a desktop browser.
Measured 1.6s on a simulated phone viewport. Google's threshold for 'good' is 2.5s.
181 links in the served HTML, 186 after rendering — navigation is discoverable.
Cumulative Layout Shift measured at 0.000 (good is 0.1 or less).
The page fits the mobile viewport with no sideways scrolling.
0 long JavaScript task(s) blocked the main thread while loading.
| Final URL | https://stripe.com/ie |
|---|---|
| Host IPs | 198.137.150.161, 198.202.176.161 |
| Pages crawled | 12 of 12 attempted |
| Sitemap URLs | 0 |
| Nameservers | ns-1087.awsdns-07.org, ns-1882.awsdns-43.co.uk, ns-423.awsdns-52.com, ns-705.awsdns-24.net |
| Mail servers | alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com |
| DKIM selectors | google, s1, s2, mandrill |
| Mail server IPs | 172.253.157.26, 142.250.102.27, 74.125.193.26 |
| TLS | TLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by DigiCert Inc |
| Detected stack | Next.js / origin / Route 53 · mail on Google Workspace |
| Browser render | Camoufox (stealth Firefox) · 7.6s · 2124 words, 186 links after JavaScript |
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.
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 stripe.com first.