{ "url": "https://bloxx.page/home", "title": "Bloxx Pages: publish from your AI, optimised on arrival", "description": "Publish a page from Claude in one line. It goes live with schema and meta correct, and is served as .md, .txt, .json and .schema at the same URL.", "lang": "en-GB", "headings": [ { "level": 1, "text": "Publish a page from your AI in one line" }, { "level": 2, "text": "The gap this fills" }, { "level": 2, "text": "What is live today" }, { "level": 3, "text": "Publish" }, { "level": 3, "text": "Score" }, { "level": 3, "text": "Measure" }, { "level": 3, "text": "Serve to machines" }, { "level": 2, "text": "One connector for the whole site" }, { "level": 3, "text": "publish_page" }, { "level": 3, "text": "audit_site, compare_sites" }, { "level": 3, "text": "search_console_performance" }, { "level": 3, "text": "striking_distance" }, { "level": 3, "text": "analytics_overview, traffic_sources" }, { "level": 3, "text": "ai_referral_report, bot_traffic_report" }, { "level": 2, "text": "The page language" }, { "level": 2, "text": "Formats and modifiers" }, { "level": 2, "text": "Early access" } ], "links": [ { "text": "How it works", "href": "#how" }, { "text": "Read the language spec", "href": "/bloxx-markdown" }, { "text": "/home", "href": "/home" }, { "text": ".md", "href": "/home.md" }, { "text": ".txt", "href": "/home.txt" }, { "text": ".json", "href": "/home.json" }, { "text": ".schema", "href": "/home.schema" }, { "text": "language spec", "href": "/bloxx-markdown" }, { "text": "/bloxx-markdown", "href": "/bloxx-markdown" }, { "text": ".md", "href": "/bloxx-markdown.md" }, { "text": ".txt", "href": "/bloxx-markdown.txt" }, { "text": ".json", "href": "/bloxx-markdown.json" }, { "text": ".schema", "href": "/bloxx-markdown.schema" }, { "text": "formats reference", "href": "/formats" }, { "text": "Email hello@itsbloxx.com", "href": "mailto:hello@itsbloxx.com" }, { "text": "Run a free audit", "href": "https://itsbloxx.com/r/audit" } ], "text": "Bloxx Pages\n\n Running on 27+ live domains\n\n Publish a page from your AI in one line\n\n The page is live in seconds, with title, description, canonical and JSON-LD already correct. Then it is served as .md, .txt, .json and .schema at the same URL, for anything that reads pages by machine.\n\n How it worksRead the language spec\n\n This page, in four machine formats\n\n /home.md.txt.json.schema\n\n Click any of them. Same content, same URL, served the way a crawler or an agent asks for it. Every page published through Bloxx gets this, cached at the edge.\n\n27+\nlive domains served by the Bloxx renderer today\n\n4\nmachine formats at every URL, no configuration\n\n10\ntools in the connector, from publish to AI-crawler share\n\nThe gap this fills\n\nNetlify Drop, tiiny.host and Claude artifact sharing all solve hosting. None of them touch the page on the way through. You get a link, and the page ships with whatever meta, heading structure and structured data the generator happened to emit, which for AI-generated HTML is usually none.\n\nBloxx treats publishing as the moment to fix that, because it is the only moment where the fix is free. The page is already in a pipeline, so scoring it, repairing the head, and exposing it in machine formats costs the user nothing and no extra step.\n\nBeing precise about status, because it matters more than a tidy story: the publish loop, the format views, the audit engine, the analytics tools and Bloxx Markdown are live and in daily use across the fleet. Audit-on-publish, custom domains and lead capture are next, not done.\n\nWhat is live today\n\n- 1Publish\none connector call, or one paste of a full HTML document. The page is a live URL on bloxx.page in seconds, and republishing the same slug updates that page instead of making a duplicate.\n\n- 2Score\nthe audit engine reads any live URL and returns overall, schema, LLM-readability and semantics scores, with the specific findings behind each one.\n\n- 3Measure\nevery request to every Bloxx domain is classified at the edge, so AI crawlers show up separately from search crawlers, SEO tools and humans.\n\n- 4Serve to machines\n.md, .txt, .json and .schema are generated from the same page and cached at the edge, so an agent takes the format it wants without scraping HTML.\n\nOne connector for the whole site\n\nThe part that is genuinely hard to assemble yourself is not the hosting. It is having publishing, optimisation scoring, Search Console, GA4, AI referral traffic and crawler data available in one place, to one agent, in one session. That is the connector.\n\npublish_page\ntakes a full HTML document and returns a live URL. Idempotent on the slug, purges the edge cache on write.\n\naudit_site, compare_sites\nschema, LLM-readability and semantics scores for any URL, with findings, quick wins and an action plan.\n\nsearch_console_performance\nclicks, impressions, position and CTR from Search Console, by query, page, country or device.\n\nstriking_distance\nthe queries sitting at positions 5 to 20, ranked by how much click opportunity is actually available.\n\nanalytics_overview, traffic_sources\nGA4 sessions, users and conversions, with an AI-referred segment split out.\n\nai_referral_report, bot_traffic_report\nwhat arrives from ChatGPT, Perplexity, Gemini and Copilot, and which AI crawlers are reading the site.\n\nPoint it at a domain and ask what is wrong with it. The answer comes back from the audit engine, Search Console, GA4 and the edge logs together, which is the part no single free MCP server does.\n\nAdd the connectorjson\n{\n \"mcpServers\": {\n \"bloxx\": {\n \"url\": \"https://mcp.bloxx.page/mcp\"\n }\n }\n}\n\nThe page language\n\nProse is ordinary Markdown. Structure comes from directives that expand to pre-built, already-optimised HTML, and the structured ones emit their own JSON-LD. A pricing block becomes a Product with an Offer. An FAQ block becomes a FAQPage. Nobody writes schema by hand, and nobody forgets it.\n\nThe page you are reading, in Bloxx Markdownbloxx-markdown\n:::hero{title=\"Publish a page from your AI in one line\" cta=\"How it works\" href=\"#how\"}\n\n:::formats{url=\"/home\" label=\"This page, in four machine formats\"}\n\n:::faq\n- Q: Is the page live instantly? A: Yes, in seconds.\n- Q: Can an agent read it? A: Every page is also .md, .txt, .json and .schema.\n:::\n\nThat is the whole idea. An agent writes a few lines instead of four hundred lines of HTML, and what comes out is consistent, styled and schema-correct because the components carry their own structured data. The language spec has the grammar and the full catalogue.\n\nFormats and modifiers\n\nOne URL grammar, applied the same way to every page: formats as a suffix, modifiers as a query. Learn it once, use it everywhere.\n\n Try it on another page\n\n /bloxx-markdown.md.txt.json.schema\n\n The format views are not a per-page feature you switch on. They are a property of the renderer, so every page on every Bloxx domain has them. The formats reference covers the full grammar.\n\nWhat does born optimised actually mean?The head is correct on arrival: title, meta description, canonical, robots, Open Graph and a JSON-LD graph assembled from the page's own components, rather than left to whatever the generator emitted.\n\nDo I have to use Bloxx Markdown?No. A full HTML document publishes as-is and still gets the format views, the edge caching and the audit engine. The language is for when you want an agent to write pages cheaply and consistently.\n\nHow is this different from MDX or Markdoc?The grammar is deliberately similar and that is the point, because models already write it. The difference is the compile target: an optimised page plus its JSON-LD plus machine formats plus hosting, rather than a React component tree you still have to build and deploy.\n\nWhy does the AI-crawler data matter?AI referral traffic is still a small share of all traffic, but it converts better than most channels, and crawler visits are the leading indicator of it. Reading them at the edge is the earliest signal available that an answer engine has started paying attention.\n\nCan I use my own domain?Not yet. Pages publish under bloxx.page today; custom domains are the next piece of table stakes.\n\n Early access\n\n The connector is live and the publish loop is in daily use across the fleet. If you build or manage sites and want to try it, get in touch.\n\n Email hello@itsbloxx.comRun a free audit\n", "schema": [ { "@context": "https://schema.org", "@graph": [ { "@type": "WebPage", "name": "Bloxx Pages: publish from your AI, optimised on arrival", "description": "Publish a page from Claude in one line. It goes live with schema and meta correct, and is served as .md, .txt, .json and .schema at the same URL.", "url": "https://bloxx.page/home" }, { "@type": "HowTo", "name": "Publishing a page through Bloxx", "step": [ { "@type": "HowToStep", "position": 1, "name": "Publish", "text": "one connector call, or one paste of a full HTML document. The page is a live URL on bloxx.page in seconds, and republishing the same slug updates that page instead of making a duplicate." }, { "@type": "HowToStep", "position": 2, "name": "Score", "text": "the audit engine reads any live URL and returns overall, schema, LLM-readability and semantics scores, with the specific findings behind each one." }, { "@type": "HowToStep", "position": 3, "name": "Measure", "text": "every request to every Bloxx domain is classified at the edge, so AI crawlers show up separately from search crawlers, SEO tools and humans." }, { "@type": "HowToStep", "position": 4, "name": "Serve to machines", "text": ".md, .txt, .json and .schema are generated from the same page and cached at the edge, so an agent takes the format it wants without scraping HTML." } ] }, { "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What does born optimised actually mean?", "acceptedAnswer": { "@type": "Answer", "text": "The head is correct on arrival: title, meta description, canonical, robots, Open Graph and a JSON-LD graph assembled from the page's own components, rather than left to whatever the generator emitted." } }, { "@type": "Question", "name": "Do I have to use Bloxx Markdown?", "acceptedAnswer": { "@type": "Answer", "text": "No. A full HTML document publishes as-is and still gets the format views, the edge caching and the audit engine. The language is for when you want an agent to write pages cheaply and consistently." } }, { "@type": "Question", "name": "How is this different from MDX or Markdoc?", "acceptedAnswer": { "@type": "Answer", "text": "The grammar is deliberately similar and that is the point, because models already write it. The difference is the compile target: an optimised page plus its JSON-LD plus machine formats plus hosting, rather than a React component tree you still have to build and deploy." } }, { "@type": "Question", "name": "Why does the AI-crawler data matter?", "acceptedAnswer": { "@type": "Answer", "text": "AI referral traffic is still a small share of all traffic, but it converts better than most channels, and crawler visits are the leading indicator of it. Reading them at the edge is the earliest signal available that an answer engine has started paying attention." } }, { "@type": "Question", "name": "Can I use my own domain?", "acceptedAnswer": { "@type": "Answer", "text": "Not yet. Pages publish under bloxx.page today; custom domains are the next piece of table stakes." } } ] } ] }, { "@context": "https://schema.org", "@type": "Person", "name": "Charlie Bailey", "jobTitle": "Founder, Bloxx Pages", "url": "https://www.linkedin.com/in/charliebaileyy/", "sameAs": [ "https://www.linkedin.com/in/charliebaileyy/", "https://x.com/joinsidequester" ] } ] }