Pigeon Documents SEO Teardown: A Clean Foundation Built on 4 Pages

Crawl data as of February 18, 2026. Analysis powered by redCacti.

Pigeon Documents does one thing really well: automated document collection for B2B teams. No client login required, syncs with your existing platforms, handles the chasing so you don’t have to.

Their website reflects a different priority. The main marketing site has 4 pages. No blog. No use case pages. No comparison content. A 101-page docs site sits on a subdomain with zero Open Graph tags, zero Twitter cards, and no schema on any page across the entire crawl.

There’s no metadata disaster here. No broken links. Image alt text on the main site is perfect. But a clean technical foundation with nothing to rank is still a dead end for organic search.

What We Crawled

Pigeon Documents runs across three distinct domains, each serving a different purpose:

Crawl summary:

• pigeondocuments.com - 4 pages (homepage, privacy policy, support, terms)
• www.pigeondocuments.com - 4 pages (exact mirrors of the above)
• docs.pigeondocuments.com - 101 pages (API reference and documentation)
• app.pigeondocuments.com - 1 page (login, noindex)
• Total: 110 pages crawled

The marketing site is a 4-page brochure. The docs site is where most of the content actually lives.

Section 1: The Content Footprint Problem

4 pages.

That’s the entire searchable content surface for a B2B SaaS product competing for document collection, client portals, and workflow automation queries. No blog, no use case pages, no integrations landing pages, no competitor comparisons.

The homepage has 665 words. Support has 281. Privacy and terms are boilerplate.

For context: most SaaS companies at the seed and Series A stage invest heavily in content because organic search is one of the few channels that compounds over time. At 4 pages, Pigeon is entirely dependent on paid acquisition, direct outreach, and word of mouth. Nothing is working for them while they sleep.

What they’re leaving uncaptured: Queries like “automated document collection software,” “how to collect client documents without login,” “document request software for accountants” are all reachable with moderate effort. Right now, there’s nothing on pigeondocuments.com to compete for any of them.

Takeaway: Content is the highest-leverage investment Pigeon can make right now. A single well-written use case page targeting a specific vertical (accounting firms, mortgage brokers, HR teams) would immediately expand their indexed footprint and capture intent that no amount of technical SEO can fix.

Section 2: Metadata Duplication Across the Main Site

The main site metadata is working on the homepage. The title is specific, the description is clear, and both OG and Twitter card tags are in place.

The three non-homepage pages tell a different story.

Privacy policy, support, and terms of service all share the same title and description as the homepage:

“Automated Document Collection | Pigeon Documents” “Stop chasing clients for documents. Pigeon automates the process from end-to-end…”

From Google’s perspective, these are three pages claiming to be about the same thing. That’s not how Google reads them - it knows the difference between a legal document and a product homepage - but it signals that the site hasn’t been configured beyond the homepage.

The same duplication carries through to OG and Twitter Card tags. If someone shares the privacy policy on LinkedIn, they see the homepage description. It’s a small thing in isolation, but it reflects a broader pattern: metadata was set up for the homepage and never extended elsewhere.

Benchmark context: This kind of duplication is extremely common on small marketing sites where the CMS applies a single global metadata template without page-level overrides. It’s also one of the simplest things to fix.

Takeaway: Each page needs a title and description that reflects its actual content. Support page: describe what support looks like. Privacy policy: a one-line description of what it covers. These won’t move rankings, but they prevent confusion in search and social previews.

Section 3: www vs Non-www Duplication - 4 Page Pairs, No Canonicals

Both pigeondocuments.com and www.pigeondocuments.com return 200 OK for the same 4 pages. The content is identical. The word counts match. Neither version has a canonical tag pointing to the other.

Without a canonical or a redirect, Google has to decide which version to treat as authoritative. Any backlinks pointing to the www version and any pointing to the non-www version are counted separately, splitting whatever link equity exists between two versions of the same content.

For a site with only 4 marketing pages, every backlink matters. Fragmenting that signal across two domains is a problem worth solving immediately.

How to fix it: Pick one version and 301 redirect the other. Add a canonical tag on all pages pointing to the chosen version. This is a one-time DNS or hosting configuration change. Given that pigeondocuments.com has slightly more incoming links (4 vs 20 - the www version actually leads on that metric), the choice depends on where most backlinks currently point.

Section 4: Schema Markup - Zero Pages, Zero Types

The crawl found no schema markup on any page across all 110 URLs.

Not on the homepage. Not on the docs site. Not anywhere.

For a product in the document management and workflow automation space, this is a missed opportunity on several fronts:

• Organization schema on the homepage helps Google understand the company, its name, URL, logo, and social profiles. It’s a 10-minute implementation.
• WebApplication schema on the homepage signals to Google that this is a software product - relevant for app-specific SERP features.
• FAQPage schema would be ideal for a support page, potentially triggering accordion rich results.
• TechArticle or HowTo schema on docs pages could improve how documentation appears in search results.

Benchmark context: Even among small SaaS sites, schema is increasingly common as a baseline technical signal. Having zero schema across the entire domain is unusual at any stage.

Takeaway: The fastest win here is adding Organization and WebApplication schema to the homepage. It’s a 30-minute task, it’s permanent, and it gives Google cleaner structured signals about what the product is.

Section 5: The Docs Site - 101 Pages, Completely Dark

docs.pigeondocuments.com has 101 pages of API reference documentation covering requests, templates, webhooks, documents, contacts, authentication, and integrations.

Every one of those pages is missing:

• Open Graph tags (0 of 101 pages)
• Twitter Card tags (0 of 101 pages)
• Schema markup (0 of 101 pages)

When someone shares a docs page on social media, there’s no preview - no title, no description, no image. The platform renders a blank card or pulls random text from the page.

Beyond social sharing, the docs content itself has significant structural issues:

Title = Meta Description on 100% of docs pages. Every page uses the format “Page Name - Pigeon” for both the title tag and the meta description. “Authentication - Pigeon” as a meta description tells Google and users nothing about what the authentication page actually covers.

53 of 100 HTML docs pages are under 100 words. Many of these are API type reference pages - schema definitions, enum values, error models - with as few as 2 words of content. These pages are indexed but contribute almost nothing to search visibility.

Word count breakdown across docs:

• Average: 80 words
• Minimum: 2 words (13 pages at exactly 2 words)
• Maximum: 2,484 words (Webhooks page)
• Pages under 100 words: 53 of 100 (53%)

The Webhooks page stands out at 2,484 words. It’s the kind of thorough technical documentation that can actually rank for developer queries. The rest of the docs sit in a thin-content zone that adds crawl load without meaningful search value.

The opportunity: Developer documentation is genuinely useful to people searching for how to automate document workflows via API. With OG tags, unique meta descriptions, and TechArticle schema added at the template level, the docs site could become a real organic asset for developer-audience queries. Right now it’s invisible to search engines and social media alike.

Section 6: What Pigeon Gets Right

This teardown has focused on gaps, but a few things genuinely stand out:

Zero broken links. Across 110 pages, the crawl found no broken internal links and no broken external links. For a site with an active docs section, that’s not trivial to maintain.

100% image alt text on the main site. The homepage has 81 images, all with alt text. Privacy, support, and terms each have 2 images, all covered. That’s thorough work, especially on a homepage with that many visual elements.

The docs site has a different story - 5.7% alt text coverage across 106 images - but the main site is clean.

No crawl errors. Every page in the crawl returned 200 OK (except the noindexed login page, which is intentional). The site is stable and accessible.

These aren’t small things. A clean, error-free technical foundation is the right starting point. The problems Pigeon is carrying are about coverage and content, not about broken infrastructure.

How Pigeon Can Think About Optimization

Quick Wins

• Choose www or non-www as canonical and implement 301 redirects for the other
• Add canonical tags to all main site pages pointing to the chosen version
• Add Organization and WebApplication schema to the homepage
• Write unique title tags and meta descriptions for privacy, support, and terms pages
• Add OG and Twitter Card templates to the docs site (one template change covers all 101 pages)

Next Phase

• Write page-specific meta descriptions for docs pages instead of mirroring the title
• Add TechArticle or HowTo schema to docs page templates
• Publish 2-3 use case landing pages targeting specific verticals (accounting, legal, HR, mortgage)
• Review the 53 thin docs pages - consolidate API type stubs or expand them with usage examples

Final Action Items

• Build a blog targeting document collection and workflow automation queries
• Develop comparison pages against competing tools in the document request space
• Create integration-specific landing pages for the integrations Pigeon supports
• Fix image alt text on the docs site (5.7% coverage needs a bulk remediation pass)

Key Takeaways

• 4 marketing pages means zero organic surface area for product discovery - content is the gap, not technical SEO
• 3 non-homepage pages share the homepage title and description verbatim - a quick fix with real signal value
• 4 www/non-www duplicate pairs with no canonical tags are splitting link equity on an already small backlink profile
• Zero schema across 110 pages - no Organization, no WebApplication, no FAQ, nothing
• 101 docs pages with no OG or Twitter tags - a complete social sharing and metadata blind spot
• Zero broken links and 100% main site image alt coverage - the technical foundation is solid

Pigeon Documents has built something that clearly works as a product. The web presence reflects a company that’s focused on building the product first and marketing second. That’s a reasonable call early on - but the gap between what they have and what they need for organic search to contribute to growth is significant. The good news is that most of it is fixable in weeks, not months.

Want to run a crawl like this on your own site? Try redCacti →