Skip to content
https://pipedrive.com

SEO

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

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

Checks
7
5 PASS 1 REVIEW
B
Canonical URL
Minor issues
REVIEW
Minor issues
Info::
Canonical tag present
Got: https://www.pipedrive.com
Warning::
Canonical does not match final URL (https://www.pipedrive.com/es-es)
Info::
Canonical target returns 200
Warning::
Canonical URL redirects
A canonical URL that redirects sends mixed signals to search engines.
Info::
Canonical points to a different domain
Canonical URL Configured
Page URL https://pipedrive.com Canonical https://www.pipedrive.com Match Points to a different page Target 200 ✓

A canonical URL that redirects sends mixed signals to search engines.

Why this matters

A canonical URL that itself redirects sends mixed signals to Google — link equity may not consolidate as intended.

Learn more

When the canonical link points to a URL that 301-redirects elsewhere, Google has to choose: follow the canonical chain or treat the redirect as authoritative. Behavior is inconsistent. Set canonical to the FINAL destination URL (post-redirect) so the signal is unambiguous.

Source: Google Search Central

A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: Sales CRM & Pipeline Management Software | Pipedrive
Info::
Title length (52 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"Sales CRM & Pipeline Management Software | Pipedrive"

52 characters Optimal ✓
Title: Sales CRM & Pipeline Management Software | Pipedrive
H1: The easy and effective CRM for closing deals
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
Content Depth
3302 words, Difficult
PASS
3302 words, Difficult
Info::
Page has 3302 words — good depth for search engines
Info::
Text-to-HTML ratio is 4%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 13)
3302 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 13

Text-to-HTML Ratio

4% text 96% HTML

21 KB / 511 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
67 images, 66 descriptive filenames
PASS
67 images, 66 descriptive filenames
Info::
1 image(s) have hash/generic filenames
66 descriptive
0 hash-based
1 generic
67 total
FilenameQualityAltIssues
g2-2-2025.pnggeneric1
Current: g2-2-2025.png
Suggested: awards.png

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
5 schema types detected
PASS

Rich result eligibility

BreadcrumbList Eligible

Breadcrumb trail

Organization Eligible

Organization knowledge panel

FAQPage Eligible

FAQ rich results

Product Eligible

Product snippets

Detected schema types

BreadcrumbList json-ld → Breadcrumb trail
1/1 required
Required fields (Google)
  • itemListElement — Required — the breadcrumb chain renders nothing without this
Google's spec for this type
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 — Add ContactPoint with telephone and contactType Enables direct contact from the knowledge panel
  • description — Used as the panel summary
Google's spec for this type
WebPage 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
Product json-ld → Product snippets
2/2 required · 4/6 recommended
Required fields (Google)
  • name — Required for any product rich result to render
  • image — Required so Google can show the product thumbnail
Recommended fields
  • aggregateRating — Enables star ratings in search results
  • review — Add at least one review with author and reviewRating Enables review snippets under the result
  • offers — Enables price + stock badges in search
  • brand — Improves Knowledge Graph linking and brand recognition
  • description — Used as the snippet text under the title
  • sku — Add the SKU or merchant identifier Helps Google match products across sellers
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

Adding these recommended fields improves chances of getting Product snippets 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