SEO report for www.iheart.com

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to iheart.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✓

  XML sitemaphigh

  Sitemap index found at https://www.iheart.com/sitemap.xml listing 355 sitemaps.

  Declared in robots.txt.

  No lastmod dates – add accurate ones so search engines know what changed.

• ✓

  Canonical URLhigh

  Canonical: https://www.iheart.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://iheart.com/ → https://www.iheart.com/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  iheart.com redirects to www.iheart.com.

Search snippet & sharing 46%

How the page looks in Google results and when shared.

• ✗

  Title tagcritical

  “Listen to Your Favorite Music, Podcasts, and Radio Stations for Free! – iHeart”

  About 689px of Google's ~580px desktop width – it will probably be cut off.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  252 characters, ~1496px of ~990px.

  Long – Google will probably truncate it.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en"

Content quality 80%

Is there enough clear, useful text that matches what the page targets?

• !

  Word countmedium

  279 words of main content (menus and footer excluded).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

  Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.

  Count words and keywords with the free word counter

  Read the guide: how to write SEO content

• ✓

  Readabilitymedium

  Flesch reading ease 60 (plain English), about 10 words per sentence.

• ✓

  Topic focushigh

  6 of 7 title keywords appear in the main content (missing: listen).

• ✓

  H1 headingcritical

  “All your favorite music, radio and podcasts, all free.”

• !

  Heading structuremedium

  18 headings for 279 words – a lot for the amount of text.

  2 skipped level(s), e.g. H2 → H4.

  Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  Read the guide: the on-page SEO checklist

• ✗

  Text-to-code ratiolow

  0% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 44%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✗

  llms.txtlow

  No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

  Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✗

  Question-led contentmedium

  No headings phrased as questions.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✗

  Entity clarityhigh

  No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

  Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  Freshness signalsmedium

  No published/updated date found.

  Fix: Show a 'last updated' date and add dateModified to your structured data.

• !

  Trust pages (E-E-A-T)medium

  Links found to about and privacy; missing contact.

  Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): WebSite, SearchAction.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 88%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  66 internal and 15 external links.

• !

  Anchor text qualitymedium

  Same text used for different pages: “play”.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

Performance 53%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• ✓

  Server response (TTFB)high

  69 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

• ✗

  HTML sizemedium

  433 kB of HTML – heavy for phones.

  Fix: Remove inline bloat, base64 images and unused markup.

• ✓

  Compressionmedium

  Compressed with br.

• ✓

  Render-blocking resourceshigh

  0 blocking script(s) and 0 stylesheet(s) in <head>.

• ✗

  Scripts & third partiesmedium

  77 script tag(s); files loaded from 1 other domain(s): static.adsafeprotected.com.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  9 image(s).

  9 without width/height – can cause layout shift (CLS).

  1 image(s) after the first three aren't lazy-loaded.

  The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.

  0 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  Read the guide: image SEO

• ✗

  Cachinglow

  No Cache-Control header.

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• i

  HTTP/3low

  Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 88%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✓

  HSTSmedium

  HSTS: max-age=31557600

• !

  Security headerslow

  Present: nosniff, Referrer-Policy.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✗

  Server fingerprintlow

  X-Powered-By reveals “Express”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 67%

Usable on phones and by everyone – Google indexes the mobile version.

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1, maximum-scale=5.0, user-scalable=yes

• ✓

  Image alt textmedium

  All 9 images have alt text.

• ✗

  Form labelsmedium

  1 of 1 form field(s) have no label.

  Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

• ✓

  Link nameslow

  Every link has a readable name.

• ✗

  Tap-to-contactmedium

  No tel: or mailto: links.

  Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

  Read the guide: mobile-friendly websites

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

• i

  LocalBusiness markuphigh

  No LocalBusiness structured data.

• i

  Contact details on pagemedium

  No phone number found.

  No postcode found (fine for service-area businesses).

• i

  Map & directionslow

  No map or directions link.