IndexFlow opens its Rust SEO core ahead of a commercial platform

Why it matters

IndexFlow shows how an independent developer can use narrow open-source libraries as distribution for a larger SaaS product. Wu Jian's harder task is turning technical SEO checks into a recurring workflow customers will pay to operate.

Wu Jian, an associate professor at Nanjing University of Posts and Telecommunications, has released IndexFlow, a Rust-based attempt to turn sitemap parsing, technical SEO checks and search submission workflows into reusable infrastructure.

The public release began with an initial commit on August 19th. Wu continued adding pipeline and interface work through August 28th, when he put the project in front of a wider developer audience. IndexFlow is an independent effort, according to its website and repository, and Wu's public GitHub profile is the clearest account of the person behind it.

His bet is straightforward: website indexing remains a collection of hidden jobs that developers often handle through scripts, dashboards and third-party SEO products. IndexFlow pulls some of that work into an open-source Rust stack, with a commercial platform planned above it.

That division matters. The code Wu has shipped gives developers two small, inspectable building blocks. The product he wants to build around them would handle the recurring operational work: managing websites, monitoring sitemaps, coordinating submissions and connecting with search platforms.

Two crates form the open-source wedge

The first component, indexflow-sitemap, is a Rust library for parsing sitemap files and extracting URLs. The repository describes support for XML sitemap indexes, plain-text sitemaps and protections against circular references and excessive nesting. The published documentation lists version 0.1.0.

The second, indexflow-seo, is the more opinionated piece. Version 0.1.1 evaluates HTML for signals including HTTP status, canonical URLs, noindex directives, page titles, H1 headings and meta descriptions. It also extracts JSON-LD structured data, reads OpenGraph and Twitter metadata, and audits directives for crawlers associated with OpenAI, Perplexity, Anthropic and Google.

Those checks give IndexFlow a narrower job than a general search engine. Meilisearch and Typesense help applications serve search results from indexed records. Algolia's crawler discovers website content and sends extracted data into Algolia indexes. IndexFlow is aimed at the earlier and less glamorous layer: finding a site's URLs, checking whether pages are technically indexable and preparing workflows that interact with external search engines.

The repository is also larger than the two library packages. It includes application code, database migrations and a web interface. Recent commits refer to concurrent multi-site pipelines, quota handling, batch operations and Google Search Console inspection. Commit messages document active development; IndexFlow's own roadmap still places website management, search-indexing workflows, Google Search Console and Bing IndexNow integrations in the building column.

Wu is drawing the open-core boundary early

IndexFlow's project website presents the Rust repository and crates as the available layer. Website management, search indexing and search-platform integrations are planned as the next layer, followed by AI-generated SEO reports, generative engine optimization insights, website intelligence and backlink services.

The repository is dual-licensed under MIT or Apache 2.0, giving developers broad permission to use and modify the libraries. Its README says a commercial platform will add capabilities above those components. Wu has therefore published the technical foundation while reserving the workflow, automation and hosted experience as the prospective business.

That is a familiar open-core route for infrastructure founders. Searchcraft, another Rust-based search project, has paired its engine with a managed and self-hosted product. Meilisearch offers an open-source engine alongside a cloud service. IndexFlow is entering from a different direction, using sitemap and SEO tooling as its initial distribution surface rather than building a query-serving engine first.

The approach gives Wu a practical way to test demand. Developers can adopt either crate without moving an entire search stack or entrusting a website to a new hosted service. Usage can expose which problems deserve a commercial workflow: sitemap monitoring, submission queues, quota management or reporting across multiple sites.

The commercial challenge will come from that same modularity. Sitemap parsing and metadata inspection are useful, but each can remain a library feature or an internal script. IndexFlow must make the coordination layer valuable enough that developers and website operators prefer a maintained platform over assembling the pieces themselves.

AI search gives the project its timing

Wu is positioning IndexFlow for a period when publishers and businesses are monitoring visibility across conventional search engines and AI products. The concrete work in the current SEO crate includes machine-readable metadata, structured data and crawler directives. Those are observable page properties that software can inspect consistently.

IndexFlow's larger claims around AI search are still product direction. Auditing whether a site blocks GPTBot or Google-Extended is technically defined. Measuring whether a change improves citations, referrals or visibility inside an AI answer requires data and evaluation methods beyond a crawler check. IndexFlow lists GEO insights and AI SEO reports as future work rather than presenting them as completed capabilities.

That restraint gives the early release a credible center. Wu has shipped narrow libraries for jobs developers already perform, then exposed the larger platform he intends to build around them. The next test is whether those libraries become an adoption channel for the workflow product, rather than remaining two useful Rust crates at the edge of a crowded SEO market.