Skip to content
https://vipoftalmologia.com.br

SEO

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

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

Checks
14
9 PASS 4 REVIEW
C
Content Depth
Action
619 words, Very Difficult
REVIEW
619 words, Very Difficult
Info::
Page has 619 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 15)
619 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 15

Text-to-HTML Ratio

4% text 96% HTML

4 KB / 93 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.

B
Image SEO
7 images, 3 descriptive filenames
REVIEW
7 images, 3 descriptive filenames
Warning::
57% of images have non-descriptive filenames
Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.
3 descriptive
4 hash-based
0 generic
7 total
FilenameQualityAltIssues
48bf950c-cc98-4d69-aeb4-57a2ede64449.webphash✓1
Current: 48bf950c-cc98-4d69-aeb4-57a2ede64449.webp
Suggested: assets.webp
fecedf85-bb23-4878-8f93-d157ffc824ce.webphash✓1
Current: fecedf85-bb23-4878-8f93-d157ffc824ce.webp
Suggested: assets.webp
e3fe5b9d-574d-4ecc-85cb-2941e8f8ef0b.webphash✓1
Current: e3fe5b9d-574d-4ecc-85cb-2941e8f8ef0b.webp
Suggested: assets.webp
7286f1bd-c577-46c0-9cc2-aa1522f13775.webphash✓1
Current: 7286f1bd-c577-46c0-9cc2-aa1522f13775.webp
Suggested: assets.webp

See Accessibility tab for detailed alt text quality analysis.

Search engines use filenames as a signal. Rename to descriptive names like 'team-photo.jpg'.

Why this matters

Most image filenames are non-descriptive (hash/IMG_X) — small SEO miss for Image Search ranking.

Source: Google Image SEO

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.
B
Sitemap Hygiene
1 hygiene issue(s) on a 0-URL sitemap
REVIEW
1 hygiene issue(s) on a 0-URL sitemap
Warning::
Sitemap is empty -- 0 URLs listed
The sitemap file is reachable and parses as valid XML, but contains no `<url>` entries. Common causes: a templated sitemap that didn't iterate the URL set during build, a static placeholder shipped to production, or a CMS that lost its URL index. Search engines fetch and discard empty sitemaps.
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://vipoftalmologia.com.br/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://vipoftalmologia.com.br Canonical https://vipoftalmologia.com.br/ Match Self-referencing (correct) Target 200 ✓
A
Meta Tags
Title: 70 chars
PASS
Title: 70 chars
Info::
Page title is set
Got: Vip Oftalmologia | Dr. Mário Franco - Cirurgia Refrativa em Brasília
Info::
Title is 70 characters — may be truncated in search results
Info::
Meta description is 236 characters — truncated on mobile (~160 char limit)
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Vip Oftalmologia | Dr. Mário Franco - Cirurgia Refrativa em Brasília"

70 characters Will truncate
Title: Vip Oftalmologia | Dr. Mário Franco - Cirurgia Refrativa em Brasília
H1: Vip OftalmologiaCuidando da saúde dos seus olhos
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
Title Style Depth
1 title-style issue(s) detected
PASS
1 title-style issue(s) detected
Info::
Title uses 2 different separator characters: |, -
The page title `Vip Oftalmologia | Dr. Mário Franco - Cirurgia Refrativa em ...` uses multiple separator characters (|, -). Consistent separator use is a soft signal of careful editorial control; mixed separators usually mean the title was assembled from multiple template fragments (CMS title + brand + section) without a normalization step. Pick one separator (commonly `|`, `-`, or `:`) and stick with it across the whole site.
Got: 2 separators: | -
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+
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
5 schema types detected
PASS

Rich result eligibility

FAQPage Eligible

FAQ rich results

WebSite Eligible

Sitelinks search box

Detected schema types

MedicalBusiness json-ld
0/0 required
MedicalProcedure json-ld
0/0 required
Physician json-ld
0/0 required
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type
WebSite json-ld → Sitelinks search box
2/2 required · 0/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 — Add a SearchAction with target and query-input Enables the in-SERP search box
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 Sitelinks search box 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