Shopify App Store

Fewer than two indexable pages with a title were sampled, so titles can't be compared.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Link your main pages from the homepage so crawlers (including this one) can find them.

Title found: "Shopify App Store"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title is 17 characters, inside this audit's 15–60 review range.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title "Shopify App Store" says more than the site name.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Meta description found: "Shopify App Store: customize your online store and grow your business with Shopify-approve…"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Description is 148 characters and inside this audit's 70–160 preview range.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

No page URLs were recovered from the partially inspected sitemap tree.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Check unreachable child sitemaps and rerun. Partial traversal cannot establish an empty sitemap.

The crawl reached no inner URLs, so URL readability cannot be assessed.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Link your inner pages from the homepage so they can be crawled. This check then reviews their path structure.

One canonical declaration found.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No conflicting noindex and cross-page canonical instructions.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No meta-refresh redirect.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No soft-404 pattern on sampled HTTP 200 pages.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Visible text is 3.7% of the HTML markup (scripts and styles excluded).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.

Flesch reading ease ≈ 45.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.

Need both a <title> and an H1 to compare them.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Add whichever is missing — the metadata and headings checks name it — then this check confirms the two describe the same topic.

Only one page was sampled, so there is nothing to compare.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Link your main pages from the homepage so the audit can sample and compare them.

Only one distinct content page was sampled, so repeated discovery copy cannot be compared.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Sample at least two substantial URLs so repeated descriptions, H1s, and publisher text can be checked.

No recognized empty JavaScript application shell on 1 sampled page(s). The entered page exposes 852 publisher word(s).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

og:image:width / og:image:height are missing.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Declare them (1200×630 recommended) so platforms render the preview immediately on first share instead of after re-scraping.

No og:site_name tag.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add it. Share cards use it to label the publisher; consistent naming also gives this audit a measurable entity signal. It does not measure or guarantee citations, rankings, or traffic.

og:title: "Shopify App Store"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:description: "Shopify App Store: customize your online store and grow your business with Shopify-approve…"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image is set: "https://apps.shopify.com/cdn/shopifycloud/shopify_app_store/assets/shopify-app-store-og-20%E2%80%A6"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image returns 200 (image/jpeg).

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:url and og:type ("website") are set.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

twitter:card is "summary_large_image".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

No JSON-LD structured data on the homepage.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.

No Organization, WebSite or Person schema found.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Add an identity node so search engines and AI assistants can attribute your content to a real entity.

No JSON-LD blocks were found, so there is no syntax to validate.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.

No inner pages crawled.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Not applicable until inner pages exist.

No content-specific schema (Article, Product, FAQPage…) detected.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.

The audited page has no <h1> (it starts at H2).

Headings are the outline every parser and screen reader follows to find the answer. Right now the sampled pages don't provide it.

Add one <h1> stating what the page is about, usually the hero headline. Search engines, screen readers and answer engines use it as the page's main heading.

5 heading level skips: H2 → H5 "Shopify Editions | Fall ’26"; H3 → H5 "Shopify Editions | Fall ’26"; H2 → H5 "Featured app"; ….

Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.

Use the next level down for each subsection (H2 under H1, H3 under H2). If a heading level was chosen for its font size, keep the level and change the styling instead.

3 duplicate ID occurrence(s) across 1 document(s).

Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.

Give each element a unique id and update fragment links and aria-labelledby references to point to the intended element.

• https://apps.shopify.com/

No H1 exists to check for uniqueness.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing main heading.

No H1 text exists to inspect.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing main heading.

26 headings, averaging 4.1 words — descriptive.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

11 H2 section(s) structure the page.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

4 of 40 visible images have no alt attribute (90% covered): CP7Z_quEhYkDEAE=.png, CPi6_-Sg3pADEAE=.png, ArrowRight-e8f74994b8e9f42073f01d2642428…, ….

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Add an alt attribute to each: a short description for images that carry meaning, alt="" for purely decorative ones so screen readers skip them.

• https://apps.shopify.com/

40 of 40 visible images lack width and height attributes: hero-large-b8533cc1ee4f5c0e385b2741ffef0…, hero-large-773844e23482ab7fe0fba24563484…, hero-large-b8533cc1ee4f5c0e385b2741ffef0…, ….

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Set explicit width and height so the browser reserves the space before the image loads. Without them the page shifts as images arrive, which is what Cumulative Layout Shift measures. next/image sets them for you.

37 of 37 raster images have a WebP/AVIF source or come from a format-negotiating image service.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

7/40 images are lazy-loaded.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

No same-page fragment links to check.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.

Keep section links connected to stable IDs.

All 12 sampled internal links return < 400.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

109 of 109 links have descriptive text or labels.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

No placeholder links on the audited page.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

All target="_blank" links carry rel="noopener".

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

Homepage links to 51 distinct internal pages.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

2 of 148 source controls lack a detectable name.

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.

• https://apps.shopify.com/

No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Check computed font sizes in a browser across mobile widths.

No ARIA ID references found in the sampled HTML.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Verify rendered accessibility separately.

Viewport configured: "width=device-width, initial-scale=1".

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

The viewport lets users zoom.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

34/69 images ship responsive srcset variants.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

Language declared: lang="en".

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

37 syntactically valid hreflang tags including x-default. Reciprocal links and target content were not verified.

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

Declared language (en) matches detected content language.

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

No apple-touch-icon link.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.

No web manifest linked.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Optional, but a manifest.json enables install prompts and better mobile integration.

No theme-color meta tag.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.

Favicon declared via <link rel="icon"> (https://apps.shopify.com/cdn/shopifycloud/shopify_app_store/assets/favicon-3d790b3e382c5c5d7167509177c07784a9b8324b90473d7eb43c83dc1967b97d.png).

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.