Edits by Instagram: Easy Video Creation & Editing | Edits App

Title is 61 characters, over this audit's 60-character review point (a display heuristic, not a Google limit). Google may shorten it in results.

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Front-load the distinctive topic and value so a shortened title still says what the page is. The first 57 characters read: "Edits by Instagram: Easy Video Creation & Editing | Edits…"

Title found: "Edits by Instagram: Easy Video Creation & Editing | Edits App"

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 "Edits by Instagram: Easy Video Creation & Editing | Edits Ap…" 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: "Turn your ideas into stunning videos with Edits, a new video creation app from Instagram. …"

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 142 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.

All 10 indexable sampled pages have distinct titles.

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 sitemap found (checked https://edits.instagram.com/sitemap/edits_instagram_com_sitemap.xml.gz → 403).

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Publish a sitemap.xml and submit it in Google Search Console. Next.js: export from app/sitemap.ts — it's ~10 lines.

No sitemap was found, so there are no submitted URLs to compare against.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

The sitemap check covers the missing file. Once one exists, this check confirms the URLs it lists are indexable.

No sitemap was reachable, so its contents cannot be validated.

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.

Publish /sitemap.xml with your canonical URLs. This check then validates the XML and the URLs it lists.

No sitemap was reachable, so robots.txt has nothing to point at.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Publish the sitemap first, then add a Sitemap: line to robots.txt naming its absolute URL.

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.

Visible text is 4.6% 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 ≈ 52.

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.

No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 262 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.

The audited page has about 262 words of main content.

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.

No placeholder text detected on crawled pages.

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.

No starter-template artifacts detected.

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.

No twitter:card tag.

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.

Add <meta name="twitter:card" content="summary_large_image">. X falls back to Open Graph for the rest, but the card type itself must be declared.

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.

og:title: "Edits by Instagram: Easy Video Creation & Editing | Edits App"

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: "Turn your ideas into stunning videos with Edits, a new video creation app from Instagram. …"

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://www.facebook.com/business/f/4131149643878882/"

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.

og:site_name: "Edits App".

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.

None of the 9 crawled inner pages declare BreadcrumbList schema.

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 BreadcrumbList to inner pages — Google shows breadcrumbs in results and it clarifies site structure.

• https://edits.instagram.com/tutorials/captions/
• https://edits.instagram.com/desktop/
• https://edits.instagram.com/blog/
• https://edits.instagram.com/tutorials/advanced-audio-editing-tools/
• https://edits.instagram.com/tutorials/keyframes/
• https://edits.instagram.com/tutorials/teleprompter/
• https://edits.instagram.com/tutorials/restyle/
• https://edits.instagram.com/tutorials/ideas/
• https://edits.instagram.com/tutorials/effects/

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.

4 heading level skips: H2 → H5 "SIMPLIFY YOUR PROCESS"; H3 → H5 "CREATE WITH POWERFUL TOOLS"; H3 → H5 "INFORM YOUR CREATIVE DECISIONS"; ….

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://edits.instagram.com/desktop/

H1 found: "Video editing app for creators"

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

Nothing to do here.

Exactly one H1 on the homepage.

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

Nothing to do here.

H1 reads "Video editing app for creators".

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

Nothing to do here.

15 headings, averaging 5.8 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.

5 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.

3 of 11 visible images lack width and height attributes: media, media, -PAXP-deijE.gif.

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.

None of the 11 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).

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 loading="lazy" to below-the-fold images so the initial render doesn't wait on them. Keep the hero image eager.

All 11 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.

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.

2 of 2 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.

3 of 48 links have unclear anchor text: 3 generic ("Learn more").

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.

Make each link say where it goes ("Read the pricing guide" rather than "Read more"). For icon-only links, add an aria-label. Anchor text tells crawlers and screen-reader users what the destination is about.

• https://edits.instagram.com/

9 external link(s) open in a new tab without rel="noopener".

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.

Current browsers already treat target="_blank" as noopener, so the remaining risk is limited to older browsers. Adding rel="noopener" keeps the opened page from controlling yours there too.

Same-page links point to missing source targets on 1 page(s).

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.

Match each fragment to an element ID. Verify JavaScript-created targets in the browser.

• https://edits.instagram.com/desktop/

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.

No dead placeholder links. 16 scripted control(s) use href="#" or javascript:; a <button> would describe them better to assistive technology.

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 16 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.

160 of 456 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://edits.instagram.com/
• https://edits.instagram.com/tutorials/captions/
• https://edits.instagram.com/desktop/
• https://edits.instagram.com/blog/
• https://edits.instagram.com/tutorials/advanced-audio-editing-tools/
• https://edits.instagram.com/tutorials/keyframes/
• https://edits.instagram.com/tutorials/teleprompter/
• https://edits.instagram.com/tutorials/restyle/
• https://edits.instagram.com/tutorials/ideas/
• https://edits.instagram.com/tutorials/effects/

None of the 18 images use srcset.

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

Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.

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.

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.

20 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.

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

Nothing to do here.

hreflang "es-la" uses "la", which is not an ISO 3166-1 country code.

The declared language tells browsers and assistive tech how to read the page and who it is for. It is there, but weaker than this check expects.

Use a specific country code instead (for the United Kingdom: en-GB). Google ignores hreflang values with unknown regions.

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.

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://static.xx.fbcdn.net/rsrc.php/yb/r/GUfGNlBjVjq.svg).

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

Nothing to do here.