Skip to content
https://Pennycalc.com

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
96
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://pennycalc.com/
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target reachable (self-referencing)
Canonical URL Problem
Page URL https://Pennycalc.com Canonical https://pennycalc.com/ Match Self-referencing (correct)
A
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: PennyCalc — Financial Calculators That Show the Math
Info::
Title length (54 chars) is optimal
Info::
Meta description is 161 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

"PennyCalc — Financial Calculators That Show the Math"

54 characters Optimal ✓
Title: PennyCalc — Financial Calculators That Show the Math
H1: Financial mathyou can verify.
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
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
1186 words, Very Difficult
PASS
1186 words, Very Difficult
Info::
Page has 1186 words — good depth for search engines
Info::
Reading level: Very Difficult (grade 14)
1186 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 14

Text-to-HTML Ratio

8% text 92% HTML

8 KB / 99 KB

A+
Image SEO
No images
PASS
No images
Info::
No images on this page
No images on this page.
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 (1 URLs, 184 bytes)
PASS
Sitemap structure / size look healthy (1 URLs, 184 bytes)
Info::
Sitemap structure / size look healthy (1 URLs)
A+
Markup Quality
No markup-quality issues detected
PASS
No markup-quality issues detected
Info::
No markup-quality issues detected
A+
Schema Markup Audit
3 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

FAQPage Eligible

FAQ rich results

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 1/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 — Add sameAs URLs for social profiles 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
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
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

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

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