MarketEngine
Internal system for deciding whether an SEO task is worth doing before it becomes a ticket.
Stack
FastAPI, Python, PostgreSQL/Neon, Redis, Qdrant, Docker Compose, Celery, ILCrawler evidence, SERP overlap, LLM gateway profiles
Proof angle
Shows decision-system work that joins crawler evidence, competitor facts, owned-page matching, scoring rules, and recommendation guardrails.
Overview
MarketEngine keeps market ideas, seed queries, offers, competitor pages, source payloads, SERP-overlap clusters, crawler evidence, owned-page matches, and action cards in one review layer.
Where this is relevant
Relevant for SEO action prioritization, owned-page matching, competitor and SERP evidence review, action-board systems, and technical fixes that need evidence before tickets are created.
AI / automation relevance
MarketEngine is decision support, not an automatic content writer. It narrows evidence into reviewable actions and keeps unsupported recommendations blocked.
What it shows
- market ideas, seed queries, offers, competitor pages, and source payloads in one place
- SERP-overlap grouping before deciding whether to improve an existing page or build a new one
- ILCrawler and private-crawler evidence joined with competitor facts and owned-page matches
- action cards for content, metadata, internal links, performance, and technical fixes
- guardrails that block traffic and ranking claims when evidence is not strong enough