Skip to content
https://symfony.com

SEO

· 7 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
1
PASS
5
INFO
1

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

Checks
7
5 PASS 1 REVIEW
C
Content Depth
Action
853 words, Very Difficult
REVIEW
853 words, Very Difficult
Info::
Page has 853 words of content
Info::
Text-to-HTML ratio is 4%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Difficult (grade 18)
853 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 18

Text-to-HTML Ratio

4% text 96% HTML

6 KB / 157 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+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://symfony.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://symfony.com Canonical https://symfony.com/ Match Self-referencing (correct) Target 200 ✓
A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: Symfony, High Performance PHP Framework for Web Development
Info::
Title length (59 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Symfony, High Performance PHP Framework for Web Development"

59 characters Optimal ✓
Title: Symfony, High Performance PHP Framework for Web Development
H1: Build with confidence at any scale
Match: Very different
Robots: Indexable (no restrictions)

Alignment helps users confirm they've reached the right page.

Why this matters

Title and H1 disagree significantly — Google may treat one as the canonical topic and the other as off-topic, weakening ranking.

Learn more ▾

Title is the SERP headline; H1 is the on-page headline. They should describe the same page. Large divergence (different topics, different keywords) signals confusion and Google may rewrite the title in SERP. Align both to the same primary topic.

Source: Google Search Central / on-page SEO

A+
Image SEO
1 images, 1 descriptive filenames
PASS
1 images, 1 descriptive filenames
Info::
All images have descriptive filenames
Info::
1 image(s) missing alt text — see Accessibility tab
1 descriptive
0 hash-based
0 generic
1 total
FilenameQualityAltIssues
sf-20years-wordmark-dark--dFsFxh.webpdescriptive✗1

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
7 schema types detected
PASS

Rich result eligibility

WebSite Eligible

Sitelinks search box

Organization Eligible

Organization knowledge panel

Event Eligible

Event rich results

Event Eligible

Event rich results

Event Eligible

Event rich results

Event Eligible

Event rich results

Event Eligible

Event rich results

Detected schema types

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
Organization json-ld → Organization knowledge panel
2/2 required · 2/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 — Add ContactPoint with telephone and contactType Enables direct contact from the knowledge panel
  • description — Add an organization description Used as the panel summary
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 5/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Adds trust signal in the event card
  • offers — Enables ticket booking links
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 5/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Adds trust signal in the event card
  • offers — Enables ticket booking links
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 5/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Adds trust signal in the event card
  • offers — Enables ticket booking links
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 5/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Adds trust signal in the event card
  • offers — Enables ticket booking links
Google's spec for this type
Event json-ld → Event rich results
3/3 required · 5/5 recommended
Required fields (Google)
  • name — Required for event rich results
  • startDate — Required for the event card
  • location — Required — events without location are filtered out
Recommended fields
  • description — Used as the snippet under the event title
  • image — Strongly recommended for visual prominence
  • endDate — Helps Google decide when to stop showing the event
  • organizer — Adds trust signal in the event card
  • offers — Enables ticket booking links
Google's spec for this type

Missing schema opportunities

  • easy

    Article

    Page reads as an article (long body + headline) — add Article schema

    Eligible for top-stories carousel and Discover

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