Observed Signal · May 26, 2026 · Product Launch · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
Programmatic SEO Site: 16,750 Pages with FastAPI
A developer built BSBFinder.com, a free Australian BSB number lookup tool with more than 16,750 programmatically generated pages. The site uses FastAPI, Jinja2 server-side rendering, PostgreSQL, Caddy as a reverse proxy, Docker, and runs on a single AWS Lightsail instance. Data comes from the official AusPayNet BSB registry; the pipeline extracts CSV data, enriches it with SWIFT/BIC mappings, stores timestamped snapshots to track historical changes, and upserts into PostgreSQL with indexing. Each BSB receives a unique, content-rich page (nearby branches, payment capabilities, dynamic FAQs, Schema.org markup). The project includes a free REST API (no auth for reasonable use), batch-split sitemaps for crawl management, and tools like a BSB validator and bulk lookup. The author highlights SSR, content depth, internal linking, and staged sitemap submission as key SEO lessons and plans a discontinued-BSB section and premium API tier.
Practical case study demonstrating scalable programmatic SEO, crawl management, and a public API—useful guidance for publishers and developers but not industry-shifting.
Track PostgreSQL Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- BSBFinder.com is a free Australian BSB lookup tool with over 16,750 individual pages.
- Tech stack: FastAPI (Python), PostgreSQL, Jinja2 (server-side rendering), Caddy reverse proxy, Docker, deployed on AWS Lightsail.
- Primary data source is AusPayNet (official BSB registry); pipeline extracts CSV, enriches with SWIFT/BIC, snapshots historical changes, and upserts into PostgreSQL.
- The site exposes a free REST API supporting single lookups, search, and listings without authentication for reasonable usage.
- Sitemaps exceed 20,000 URLs and are split into batches (5,000 per sitemap) and submitted over several days to manage crawling.
Connected Companies & Entities
3 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Programmatic SEO Case Study: Bing Outperforms Google 2.6×
A developer launched a 200+ page programmatic SEO site on a new .in domain using a static Next.js export deployed to Cloudflare Pages. Over ten weeks the site’s Bing traffic grew faster than Google’s, with Bing sending 2.6× more clicks than Google by week ten. The site uses a JSON-driven taxonomy and a single universal calculator engine to generate plan-specific pages and calculators. The author reports three lessons: Bing appears to reward structured data and has no prolonged sandbox, AI-generated “overviews” (search summaries) suppress clicks to explainer content, and initial organic citations (dofollow links) start the authority flywheel. Monetization remains delayed due to ad-network approvals for new domains with templated pages.
Side-Project SEO Audit: 45 Clicks in 90 Days
An SEO audit of valuefy.app — a site with 160 calculator pages run by Sampsa (CEO at AImiten) — revealed just 45 total clicks over 90 days despite extensive on-page and automation work. The author had rewritten titles/meta descriptions, deployed daily AI content routines (Claude Code), automated blog publishing, added AI-driven internal linking, and prerendered pages with Puppeteer. Search Console data showed most pages ranking on Google’s page 5–8 with modest impressions; brand queries rank poorly for the site’s own name. The audit found one actionable technical bug (duplicate og:title/og:description tags from static index.html and React Helmet), geographic mismatches in impressions (few U.S. impressions), and concluded that the primary constraint is off‑page authority (backlinks/brand signals) rather than on‑page content alone.
Programmatic SEO: 33,620 Templated Pages, Indexing Lessons
A developer published a detailed case study of building 33,620 templated, programmatic pages (US ZIP/city/state) and the challenges of getting them indexed. Only ~6,200 pages (~18%) were indexed; most others were 'Crawled, currently not indexed' (CCNI), 'Discovered, currently not indexed', or flagged soft 404. The author documents five practical lessons: templating provides structure but not unique content (the 'boilerplate ratio' matters); different internal URL types can compete for indexing; word count is a proxy for content depth; Google Search Console (GSC) indexation verdicts can be sticky and slow to recover; and branded search traffic accelerates indexation more reliably than backlinks. The post includes specific remediation steps (hand-writing top-state content, differentiating URL intent, precomputing per-page content, driving direct traffic to stuck pages) and recommends starting small with hand-written pages before scaling.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.