Catalog / yapily.com
63

SEO audit for yapily.com

Yapily - Open Banking Platform

saas

Health 63/100 (fair) · 50 pages crawled · generated 2026-07-29

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Connect to thousands of banks across 19 countries in minutes through Yapily's open banking API. Access data, process payments, and much more. What will you build?

Screenshot of yapily.com
50
pages crawled
47
indexable pages
6
errors
265
warnings
436
notices
0
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Crawlability 94 3 0 3
Sitemap 94 3 0 0
Performance 69 0 51 46
Duplicate 70 0 50 2
Links 70 0 50 3
Security 72 0 47 97
Canonical 74 0 44 2
Meta Description 93 0 11 18
Headings 96 0 6 6
Agent Readiness 98 0 3 14
Images 99 0 2 47
Video 99 0 1 0
Cache 100 0 0 47
Content 100 0 0 82
Social 100 0 0 58
Structured Data 100 0 0 7
URL 100 0 0 4
Findings

Errors (2 rules)

error Non-200 URL listed in sitemap

Rule sitemap.not_200 · Sitemap · 3 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 3 occurrence(s)

Warnings (12 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 3 occurrence(s)

warning Missing canonical tag

Rule canonical.missing · Canonical · 44 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 5 occurrence(s)

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 45 occurrence(s)

warning Missing <h1>

Rule h1.missing · Headings · 6 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 47 occurrence(s)

  • https://www.yapily.com/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/90-day-reauthentication-changes?utm_medium=online&utm_source=pr&utm_campaign=pr-certua — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/industry/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/kyc/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/open-banking-case-study-volume/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/page/2/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/payments/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/yapily-adyen-announcement/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/yapily-and-certua-team-up-to-simplify-life-insurance-with-open-banking/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/yapily/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/blog/yapily/page/2/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/company/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/company/get-started/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/confirmation/contact-success/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/faq/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/legal/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/legal/cookie-policy/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/open-banking-glossary/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/pricing/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/product/open-banking-country-coverage/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/resources/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/resources/case-studies/open-banking-case-study-emma/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/resources/glossaries/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.yapily.com/solution/fx-remittance/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Images missing alt text

Rule images.missing_alt · Images · 2 occurrence(s)

warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 4 occurrence(s)

  • https://www.yapily.com/blog/bank-on-file-how-it-works/ — the likely hero/LCP image (2705.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.yapily.com/blog/lending-webinar-intelligent-data-and-integrated-payments/ — the likely hero/LCP image (1f449.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.yapily.com/blog/open-banking-solutions/ — the likely hero/LCP image (2714-fe0f.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.yapily.com/blog/tink-alternatives-6-open-banking-platforms-compared/ — the likely hero/LCP image (2714-fe0f.png) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Internal link points to a redirect

Rule links.redirect_target · Links · 50 occurrence(s)

warning Missing meta description

Rule meta_desc.missing · Meta Description · 11 occurrence(s)

warning Render-blocking script in <head> (no defer/async)

Rule perf.render_blocking · Performance · 47 occurrence(s)

warning Video element present but hidden/zero-size (prominence)

Rule video.hidden · Video · 1 occurrence(s)

Notices (23 rules)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 13 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://www.yapily.com/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice Page served uncached (no-store/private or CDN bypass)

Rule cache.not_cacheable · Cache · 47 occurrence(s)

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 2 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 1 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 45 occurrence(s)

  • https://www.yapily.com/ — this page reads as very difficult (Flesch Reading Ease 27, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/90-day-reauthentication-changes?utm_medium=online&utm_source=pr&utm_campaign=pr-certua — this page reads as difficult (Flesch Reading Ease 35, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/industry/ — this page reads as very difficult (Flesch Reading Ease 21, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/kyc/ — this page reads as difficult (Flesch Reading Ease 30, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/open-banking-case-study-volume/ — this page reads as difficult (Flesch Reading Ease 36, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/page/2/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/payments/ — this page reads as very difficult (Flesch Reading Ease 28, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/why-chief-financial-officers-should-embrace-open-banking/ — this page reads as difficult (Flesch Reading Ease 35, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/yapily-adyen-announcement/ — this page reads as very difficult (Flesch Reading Ease 22, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/yapily-and-certua-team-up-to-simplify-life-insurance-with-open-banking/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/yapily/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/blog/yapily/page/2/ — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/company/ — this page reads as very difficult (Flesch Reading Ease 30, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/company/get-started/ — this page reads as very difficult (Flesch Reading Ease 12, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/confirmation/contact-success/ — this page reads as difficult (Flesch Reading Ease 36, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/coverage — this page reads as very difficult (Flesch Reading Ease 21, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/faq/ — this page reads as difficult (Flesch Reading Ease 31, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/open-banking-glossary/ — this page reads as difficult (Flesch Reading Ease 35, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/pricing/ — this page reads as difficult (Flesch Reading Ease 31, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/product/open-banking-country-coverage/ — this page reads as very difficult (Flesch Reading Ease 21, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/resources/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/resources/case-studies/open-banking-case-study-emma/ — this page reads as very difficult (Flesch Reading Ease 25, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/resources/glossaries/ — this page reads as very difficult (Flesch Reading Ease 26, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.yapily.com/solution/fx-remittance/ — this page reads as very difficult (Flesch Reading Ease 30, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 2 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 6 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 29 occurrence(s)

  • https://www.yapily.com/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/how-payment-platforms-can-leverage-open-banking/ — the likely hero/LCP image (rh_payments-portfolio.jpeg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/industry/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/kyc/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/open-banking-case-study-volume/ — the likely hero/LCP image (volume.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/open-banking-for-banks-and-financial-institutions/ — the likely hero/LCP image (pleo-changing-how-businesses-manage-spend.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/page/2/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/payments/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/we-are-an-accredited-living-wage-employer/ — the likely hero/LCP image (living-wage-employer.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/what-can-open-banking-do-for-proptech/ — the likely hero/LCP image (proptech_and_ob_1.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/why-chief-financial-officers-should-embrace-open-banking/ — the likely hero/LCP image (why-cfos-embrace-ob_blog_feb.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/yapily/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/blog/yapily/page/2/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/company/ — the likely hero/LCP image (about-us_h1_1.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/company/get-started/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/confirmation/contact-success/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/coverage — the likely hero/LCP image (be.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/open-banking-glossary/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/pricing/ — the likely hero/LCP image (fees.svg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/product/open-banking-country-coverage/ — the likely hero/LCP image (be.webp) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/resources/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/resources/case-studies/open-banking-case-study-emma/ — the likely hero/LCP image (yapily_x_emma_case_study_v1.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/resources/glossaries/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.yapily.com/solution/fx-remittance/ — the likely hero/LCP image (filters:format(webp)) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Images without width/height (layout shift / CLS)

Rule images.missing_dimensions · Images · 47 occurrence(s)

notice Internal link has no anchor text / accessible name

Rule links.no_anchor_text · Links · 3 occurrence(s)

notice Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 36 occurrence(s)

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 17 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 1 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 11 occurrence(s)

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 17 occurrence(s)

notice URL redirects to another URL

Rule redirect.single · Crawlability · 3 occurrence(s)

notice Deep page has no BreadcrumbList structured data

Rule schema.breadcrumb_missing · Structured Data · 7 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 50 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 47 occurrence(s)

notice Missing Twitter Card tag

Rule twitter.missing · Social · 47 occurrence(s)

notice Many query parameters

Rule url.many_params · URL · 2 occurrence(s)

notice URL is very long

Rule url.too_long · URL · 2 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://www.yapily.com/
Yapily - Open Banking Platform		 200 yes 1171 50
https://www.yapily.com/blog/
Yapily - Open Banking Platform		 200 yes 607 47
https://www.yapily.com/company/
Yapily - Open Banking Platform		 200 yes 633 47
https://www.yapily.com/company/get-started/
Yapily - Open Banking Platform		 200 yes 971 47
https://www.yapily.com/faq/
Yapily - Open Banking Platform		 200 yes 2643 47
https://www.yapily.com/legal/
Yapily - Open Banking Platform		 200 yes 587 47
https://www.yapily.com/pricing/
Yapily - Open Banking Platform		 200 yes 466 47
https://www.yapily.com/product/open-banking-country-coverage/
Yapily - Open Banking Platform		 200 yes 708 47
https://www.yapily.com/resources/
Yapily - Open Banking Platform		 200 yes 593 47
https://www.yapily.com/resources/case-studies/open-banking-case-study-emma/
Yapily - Open Banking Platform		 200 yes 409 4
https://www.yapily.com/legal/cookie-policy/
Yapily - Open Banking Platform		 200 yes 1129 1
https://www.yapily.com/blog/page/2/
Yapily - Open Banking Platform		 200 yes 602 2
https://www.yapily.com/blog/bank-on-file-how-it-works/
Yapily - Open Banking Platform		 200 yes 2694 2
https://www.yapily.com/blog/how-open-banking-removes-card-chargebacks/
Yapily - Open Banking Platform		 200 yes 2468 2
https://www.yapily.com/blog/how-to-become-an-aisp/
Yapily - Open Banking Platform		 200 yes 3084 2
https://www.yapily.com/blog/lending-webinar-intelligent-data-and-integrated-payments/
Yapily - Open Banking Platform		 200 yes 1678 2
https://www.yapily.com/blog/merchant-onboarding/
Yapily - Open Banking Platform		 200 yes 2467 2
https://www.yapily.com/blog/top-open-banking-providers/
Yapily - Open Banking Platform		 200 yes 3167 2
https://www.yapily.com/blog/yapily-adyen-announcement/
Yapily - Open Banking Platform		 200 yes 791 4
https://www.yapily.com/blog/sweeping-vrp-scalable-stable/
Yapily - Open Banking Platform		 200 yes 1020 1
https://www.yapily.com/coverage
Yapily - Open Banking Platform		 200 yes 708 2
https://www.yapily.com/blog/yapily/
Yapily - Open Banking Platform		 200 yes 565 2
https://www.yapily.com/blog/yapily/page/2/
Yapily - Open Banking Platform		 200 yes 570 2
https://www.yapily.com/blog/90-day-reauthentication-changes?utm_medium=online&utm_source=pr&utm_campaign=pr-certua
Yapily - Open Banking Platform		 200 yes 1465 1
https://www.yapily.com/blog/open-banking-case-study-crezco?campaignid=21667630271&adgroupid=&keyword=&device=c&gclid=Cj0KCQjwsJO4BhDoARIsADDv4vB8WQbpioFN9Y9PkmZVDV5xO4ZkIdhk0t9caYgCdhvGrARi-F3ox1waAlBJEALw_wcB&utm_term=&utm_campaign=PM-WBN+-+0824+-+EU+-+Instant+wallet+top-ups+Pleo&utm_source=adwords&utm_medium=ppc&hsa_acc=2082445356&hsa_cam=21667630271&hsa_grp=&hsa_ad=&hsa_src=x&hsa_tgt=&hsa_kw=&hsa_mt=&hsa_net=adwords&hsa_ver=3&gad_source=1
Yapily - Open Banking Platform		 200 yes 1343 1
https://www.yapily.com/blog/yapily-and-certua-team-up-to-simplify-life-insurance-with-open-banking/
Yapily - Open Banking Platform		 200 yes 866 1
https://www.yapily.com/blog/industry/
Yapily - Open Banking Platform		 200 yes 567 1
https://www.yapily.com/blog/open-banking-for-payroll/
Yapily - Open Banking Platform		 200 yes 2432 1
https://www.yapily.com/blog/open-banking-for-wealth-management/
Yapily - Open Banking Platform		 200 yes 2653 1
https://www.yapily.com/blog/open-banking-solutions/
Yapily - Open Banking Platform		 200 yes 2719 1
https://www.yapily.com/blog/60-second-success-story-arthur/
Yapily - Open Banking Platform		 200 yes 900 1
https://www.yapily.com/blog/we-are-an-accredited-living-wage-employer/
Yapily - Open Banking Platform		 200 yes 806 1
https://www.yapily.com/blog/igaming-payments-pay-by-bank-unlock-revenue/
Yapily - Open Banking Platform		 200 yes 2623 1
https://www.yapily.com/company/get-started?utm_source=Direct&utm_medium=Marketing+Asset&utm_term=Register+your+interest&utm_content=cVRP+One+Pager&utm_campaign=MA-RS+-+0325+-+EU+-+cVRP+One+Pager
Yapily - Open Banking Platform		 200 yes 971 1
https://www.yapily.com/contact
Yapily - Open Banking Platform		 200 yes 971 1
https://www.yapily.com/blog/payments/
Yapily - Open Banking Platform		 200 yes 597 1
https://www.yapily.com/blog/how-payment-platforms-can-leverage-open-banking/
Yapily - Open Banking Platform		 200 yes 1094 0
https://www.yapily.com/blog/kyc/
Yapily - Open Banking Platform		 200 yes 506 0
https://www.yapily.com/blog/open-banking-case-study-volume/
Yapily - Open Banking Platform		 200 yes 1199 0
https://www.yapily.com/blog/open-banking-for-banks-and-financial-institutions/
Yapily - Open Banking Platform		 200 yes 2838 0
https://www.yapily.com/blog/tink-alternatives-6-open-banking-platforms-compared/
Yapily - Open Banking Platform		 200 yes 2394 0
https://www.yapily.com/blog/what-can-open-banking-do-for-proptech/
Yapily - Open Banking Platform		 200 yes 1141 0
https://www.yapily.com/blog/why-chief-financial-officers-should-embrace-open-banking/
Yapily - Open Banking Platform		 200 yes 1919 0
https://www.yapily.com/confirmation/contact-success/
Yapily - Open Banking Platform		 200 yes 481 0
https://www.yapily.com/open-banking-glossary/
Yapily - Open Banking Platform		 200 yes 2600 0
https://www.yapily.com/resources/glossaries/
Yapily - Open Banking Platform		 200 yes 492 0
https://www.yapily.com/solution/fx-remittance/
Yapily - Open Banking Platform		 200 yes 758 0
https://www.yapily.com/confirmation/
404 - Page Not Found		 404 no 24 0
https://www.yapily.com/product/
404 - Page Not Found		 404 no 24 0
https://www.yapily.com/solution/
404 - Page Not Found		 404 no 24 0

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →