Help center audit

Pipedrive

As of Aug 2, 2026

This report comes from a public crawl of the Pipedrive help center. It covers 12,387 articles across German, Italian, Russian, Portuguese, Turkish, and Polish. Every number is read from the sitemap and the pages themselves, none of it is estimated.

Open the help center Pipedrive website

support.pipedrive.com

Start page of the Pipedrive help center, as it looked when the audit ran

Health score

fair

out of 100

Platform

ReadMe

Articles total

12,387

Content age map

One tile per article, sorted from freshest to most outdated.

The sitemap gives 100 percent of the articles the same change date, Mar 7, 2024. That is a deploy timestamp rather than an edit history, so the age of this content cannot be determined from the outside.

Changes over time

Without change dates there is no timeline to draw.

Health score

A weighted value across five areas. Anything we could not measure is left out rather than counted as a zero.

FreshnessWeight 35not measurable
StructureWeight 1592
FindabilityWeight 20100
AI readinessWeight 2046
MultilingualWeight 1068

65 of 100 weight points were measurable.

What stands out

Every statement names the number it came from.

Critical

1 finding

On Mar 7, 2024, 100 percent of all articles carry the same change date. Timestamps like that come from a deploy, not from real edits, so the age of this content cannot be measured from the outside.

Worth fixing

5 findings

There is no llms.txt, so AI systems get no curated entry point into the documentation.
The articles carry no structured data. Machines see a web page, not an article with an author and a date.
Only 0 percent of the sampled pages show a change date, so readers cannot tell whether a guide still applies.
Hungarian covers only 69 percent of the primary language, leaving roughly 174 articles untranslated.
The sitemap does not point at the translations, which makes the language versions harder for search engines to connect.

Good

1 finding

All 9 AI crawlers we checked are allowed to read this help center.

Languages

Coverage relative to the primary language. Lag measures how many days a translation trails its source.

Language	Articles	Coverage	Lag
GermanPrimary	561	100%	no data
Italian	559	99.6%	no data
Russian	557	99.3%	no data
Portuguese	555	98.9%	no data
Turkish	555	98.9%	no data
Polish	555	98.9%	no data
Dutch	555	98.9%	no data
Korean	553	98.6%	no data
Czech	553	98.6%	no data
Latvian	553	98.6%	no data
Spanish	553	98.6%	no data
Finnish	553	98.6%	no data
Norwegian Bokmål	553	98.6%	no data
Swedish	552	98.4%	no data
Ukrainian	552	98.4%	no data
Indonesian	552	98.4%	no data
Estonian	551	98.2%	no data
Japanese	551	98.2%	no data
French	548	97.7%	no data
English	538	95.9%	no data
Hungarian	387	69%	no data
Thai	387	69%	no data

Visibility to AI answers

Whether ChatGPT, Claude and Perplexity are allowed to read and cite this help center at all, and whether they can tell how current an article is.

Crawler access

GPTBotallowed
OAI-SearchBotallowed
ChatGPT-Userallowed
ClaudeBotallowed
PerplexityBotallowed
Google-Extendedallowed
Applebot-Extendedallowed
CCBotallowed
Bytespiderallowed

llms.txt

absent

Structured data

none found

Visible change date

on 0 percent of the sampled pages

Findability

Based on a sample of 36 article pages. The values describe that sample, not every single page.

97.2
Meta descriptions
97.2 percent
100
Canonical tags
100 percent
100
Exactly one H1
100 percent
97.2
Images with alt text
97.2 percent
0
Very short articles
0 percent
97.2
Feedback control
97.2 percent
97.2
Breadcrumbs
97.2 percent
8.3
Table of contents
8.3 percent

Words per article: 581 median
Images per article: 4 median
Search in the help center: present

Request your own audit

We will audit your help center, free

Drop in the URL, we crawl it and send the full report by email. Usually within two working days. Whether it gets published is your call.

A full age map of every article
Translation coverage and lag per language
Discoverability for search engines and AI answer engines

These teams document with HappySupport

How we measure

We read the help center's public sitemap, assign every URL to a language and evaluate the change date it declares. We then fetch a sample of article pages spread across the whole library and read titles, descriptions, structured data and interface controls off them. All of it runs under a clearly identifiable user agent, with pauses between requests.

Limits: change dates come from the underlying system and may have been reset in bulk during a migration. We call those days out separately. Pages that block us are left out of the sample. Nothing in this report says anything about the editorial quality of the articles.

Crawl: Crawled on Aug 2, 2026
Sample: Sample: 36 of 561 articles
Source: https://support.pipedrive.com/sitemap-index.xml

This report can be wrong

Everything here is measured automatically from public pages, so a report can misread a help center or miss part of it. If a number does not match what you know about your own help center, write to contact@happysupport.ai and we will check it and correct the report.

Pipedrive is a trademark of its respective owner. This report was produced independently and is not affiliated with Pipedrive.