Skip to content
https://apple.com

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
1
PASS
12
INFO
1

Cross-tab audit — SEO, performance, crawlability, mobile, structured data

Checks
14
12 PASS 1 REVIEW
C
Sitemap Freshness
Action
Sitemap exists but no <lastmod> entries
REVIEW
Sitemap exists but no <lastmod> entries
Info::
Sitemap has no <lastmod> entries
Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://www.apple.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Info::
Canonical points to a different domain
Canonical URL Configured
Page URL https://apple.com Canonical https://www.apple.com/ Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title: 5 chars
PASS
Title: 5 chars
Info::
Page title is set
Got: Apple
Warning::
Title is only 5 characters — consider expanding
Info::
Meta description is 172 characters — truncated on mobile (~160 char limit)
Info::
Title and H1 are identical
Consider differentiating — the title is for search results, the H1 is for the page.
Title

"Apple"

5 characters Too short
Title: Apple
H1: Apple
Match: Similar ✓
Robots: Indexable (no restrictions)

Consider differentiating — the title is for search results, the H1 is for the page.

Why this matters

Title and H1 match exactly — internally consistent but misses an opportunity to optimize each for its audience (Title for SERP CTR, H1 for on-page).

Learn more

Title and H1 don't have to be identical — and often shouldn't be. The Title competes for SERP click-through (lead with keyword + value prop), while the H1 confirms to the visitor they're on the right page (more conversational is fine). Differentiating gains both surfaces.

Source: Google Search Central / on-page SEO

A+
Title Style Depth
Title style is clean -- consistent separator, no stale year, no keyword stuffing
PASS
Title style is clean -- consistent separator, no stale year, no keyword stuffing
Info::
Title style is clean
A
Content Depth
1461 words, Difficult
PASS
1461 words, Difficult
Info::
Page has 1461 words — good depth for search engines
Info::
Text-to-HTML ratio is 2%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 13)
1461 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 13

Text-to-HTML Ratio

2% text 98% HTML

9 KB / 379 KB

Very low ratio suggests heavy framework overhead or boilerplate.

Why this matters

Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.

A+
Image SEO
103 images, 88 descriptive filenames
PASS
103 images, 88 descriptive filenames
Info::
15 image(s) have hash/generic filenames
88 descriptive
0 hash-based
15 generic
103 total
FilenameQualityAltIssues
220x54.pnggeneric1
Current: 220x54.png
Suggested: wy4kakhfpvd8pkkfu3aa.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: 3b7d6fac-0061-401c-9716-742245053fd0png.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: vxnv4mq8alxikwqtzxw-bq.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: j7bmks9reensiztyepoteg.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: kc1xx3z1qbouxe1ehdu4ta.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: tvds8ceezaczcsidqyya0a.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: e452926f-7b52-4c05-a07f-8e4939b1bf6bpng.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: cc6mmzxfzd1gvqnd6islka.png
220x54.pnggeneric1
Current: 220x54.png
Suggested: 2pvq9q1gy7cxopfxk18ew.png
470x264.jpggeneric1
Current: 470x264.jpg
Suggested: 1b8cf2eb-1858-4d53-9faa-26c6b2e6cdfcpng.jpg
470x264.jpggeneric1
Current: 470x264.jpg
Suggested: 45899847-e52c-44a1-9ce5-09aedebb7a78png.jpg
470x264.jpggeneric1
Current: 470x264.jpg
Suggested: mech0329artworkenid3198591png.jpg
470x264.jpggeneric1
Current: 470x264.jpg
Suggested: 9388d284-2a0b-43e8-86e0-5852e8559d18png.jpg
470x264.jpggeneric1
Current: 470x264.jpg
Suggested: f5d65ff0-aa7d-452a-9b78-fcaf4bd6f044png.jpg
470x264.jpggeneric1
Current: 470x264.jpg
Suggested: 85a24e2f-a12f-443a-a5c1-ddd78b076bc2png.jpg

See Accessibility tab for detailed alt text quality analysis.

A+
Hreflang URL Quality
No hreflang tags on the page
PASS
No hreflang tags on the page
Info::
No hreflang tags on the page
A+
Hreflang Completeness
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
PASS
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
Info::
No hreflang tags found -- completeness check is N/A
A+
Sitemap × Robots Consistency
No sitemap-vs-robots conflicts detected
PASS
No sitemap-vs-robots conflicts detected
Info::
Sitemap URLs are not blocked by robots.txt
A+
Sitemap Hygiene
Sitemap structure / size look healthy (47 URLs, 4 KB)
PASS
Sitemap structure / size look healthy (47 URLs, 4 KB)
Info::
Sitemap structure / size look healthy (47 URLs)
A+
Markup Quality
1 markup-quality issue(s) detected
PASS
1 markup-quality issue(s) detected
Info::
1 redundant ARIA role attribute(s) on native semantic element(s)
The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.
A+
Schema Markup Audit
3 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 3/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — Connects the entity across the web
  • contactPoint — Enables direct contact from the knowledge panel
  • description — Add an organization description Used as the panel summary
Google's spec for this type
WebSite json-ld → Sitelinks search box
2/2 required · 1/1 recommended
Required fields (Google)
  • name — Required for the sitelinks search box
  • url — Required to anchor the search box to your domain
Recommended fields
  • potentialAction — Enables the in-SERP search box
Google's spec for this type
WebPage json-ld
0/0 required

Missing schema opportunities

  • moderate

    VideoObject

    Page embeds video content that could be marked up as VideoObject

    Videos appear in the video carousel and have a thumbnail badge

Adding these recommended fields improves chances of getting Organization knowledge panel in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Hreflang
0 hreflang tags
INFO
0 hreflang tags

No hreflang tags detected.

Hreflang tags are only needed for multilingual or multi-regional sites.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback