Web infrastructure for AI agents.

Key takeaways

This page covers: To sift: to pass through a sieve.; The page is now source material for an answer.; An agent translates. You approve. Only bots see it.; Teams whose customers ask an assistant first.; Page level, human in the loop, measured.; The people behind SiftServe.; Where SiftServe operates from.; Talk to us..

• SiftServe is web infrastructure that translates an existing website into an agent-readable version — semantic HTML, extracted facts, FAQs, and structured data — approved by a human before it is served to AI and bot traffic.
• This page is for anyone evaluating SiftServe as a vendor: marketing leaders, SEO/GEO practitioners, and technical decision-makers whose customers now ask an assistant before they visit a website.
• 57.5% of web traffic is already bots (Cloudflare Radar, June 2026), and no major AI crawler executes JavaScript (Vercel × MERJ server-log study, December 2024).
• Sifted pages use roughly 90% fewer tokens than typical JavaScript-heavy originals while carrying more readable content — 37% more even on an already clean static page.
• The siftserve.com homepage itself runs sifted: 32 KB against a 368 KB original (a 91% reduction) with 96% coverage.
• The service is currently offered as an eight-week free pilot on one domain, with a before-and-after audit score and per-page capture statistics reported at week eight.

To sift: to pass through a sieve.

Bakers sift flour and prospectors sift gravel for the same reason: keep what matters, let the rest fall away. A web page carries chrome, scripts, and cookie banners that an AI agent has no use for; what the agent needs is the substance underneath. That is the work this product is named for, and it gives the site its vocabulary:

The page is now source material for an answer.

Search is shifting from clicks to answers. People increasingly ask AI assistants and answer engines, and those systems read the web on the user's behalf. 2.5 billion people get AI answers every month (Google I/O 2026 keynote), 57.5% of web traffic is already bots (Cloudflare Radar, June 2026), and when Google shows an AI summary, clicks on traditional results fall from 15% to 8% of visits (Pew Research Center, 2025). Whether a brand appears in that answer, and appears accurately, depends on what a machine can retrieve from the page in a single fetch.

Websites built for human readers and traditional crawlers are poorly suited to that role. No major AI crawler executes JavaScript (Vercel × MERJ server-log study, December 2024), so client-rendered content never reaches the model; 57% of top sites show AI crawlers a nearly empty page (ModPageSpeed top-1,000 site test, May 2026). Where content does arrive, it is wrapped in navigation, scripts, cookie banners, and repeated boilerplate that consume the retriever's token budget before it reaches the substance, and facts held inside images never arrive at all. Ask an assistant about your own company and you see the result: pricing quoted from an old page, a product line described from fragments, a competitor's framing repeated as fact, or no mention at all.

An agent translates. You approve. Only bots see it.

SiftServe adds a machine-readable content layer to an existing website without changing the website. It works in four steps.

Learn the brand

We crawl your sitemap and compile a company profile and voice guidelines from your own pages ("We crawl your sitemap and compile a company profile and voice guidelines from your own pages. Both editable by you."). Both stay editable by you, and they anchor every later step so generated content stays consistent with how you describe yourself.

Translate each page

An agent rebuilds the page as semantic HTML whose headings carry the structure, facts stated plainly in text, FAQ pairs in the form people ask them, and Schema.org structured data ("An agent rebuilds the page: semantic HTML, FAQs, structured data."). A vision pass reads facts that live only in images ("A vision pass catches facts locked inside images."). It rephrases what the page already asserts — restructuring only what your pages already assert; it never adds claims.

You approve

Annotate the draft inline; the agent revises with full memory of your feedback. Every claim traces one-to-one to your original — SiftServe defines 100% coverage as every claim in the original page being present in the sifted copy through this 1:1 trace check, and the audit fails a draft that drops a fact (How we measure the capture stats). Each page is schema-validated and audit-scored, every version is immutable, and every change request is tracked to resolution. Anything not carried over is itemised for your sign-off rather than silently dropped. Nothing publishes without you.

Serve to bots

An edge worker in front of your domain identifies AI and bot traffic by user agent and serves the approved sifted page at the same URL. Humans, and search-engine crawlers such as Googlebot and Bingbot, keep getting your original page. No code changes, removable anytime.

Why this changes what gets retrieved

A retriever does not read a page the way a person does: it fetches once, on a token budget, and parses whatever is in the HTML it receives. A sifted page puts the substance in that first fetch, with facts in plain text, structure in headings and lists, entities and relationships in structured data, and answers already paired with their questions. Fewer tokens spent on boilerplate means more of the page fits in the model's context; explicit facts and structure mean the passage retrieved is the one you wrote, so a citation points at your page and says what your page says.

Measured on typical JavaScript-heavy commercial pages, sifted pages use roughly 90% fewer tokens than the originals while carrying more readable content, 37% more even on an already clean static page. The methodology is published in How we measure the capture stats, the page describing the coverage and token-reduction methodology, and every page ships with a measured before-and-after audit score ("Every page ships with a measured before-and-after audit score."). Every sifted page is checked twice against the same 80-item CORE-EEAT standard — once for the original page, once for the sifted copy AI reads ("Every page is checked twice using the same 80-item CORE-EEAT standard."). That standard scores a Total Score as the average of a GEO Score and an SEO Score ("Total Score = (GEO Score + SEO Score) / 2"), and individual criteria set concrete thresholds: coverage of at least three query variants, at least five precise numbers with units, and at least one external citation per 500 words ("Query Coverage Agent Covers ≥3 query variants (synonyms, long-tail)", "Data Precision Agent ≥5 precise numbers with units (%, $, ms)", "Citation Density Agent ≥1 external citation per 500 words").

Teams whose customers ask an assistant first.

SiftServe is built for organisations whose customers now ask an assistant before they visit a website. In practice that means three buyers: marketing leaders responsible for how the brand is represented in AI-generated answers, SEO and GEO practitioners who need a page-level mechanism beyond schema markup and llms.txt, and technical decision-makers who have to approve anything deployed in front of the domain. The prerequisites are a live domain, someone with authority to approve content, and a willingness to measure results. The service is currently offered as an eight-week free pilot on one domain.

Page level, human in the loop, measured.

We work at the page level, not the site level. A sitewide llms.txt tells an agent where to look; it does not change what the agent finds when it arrives. Rendering JavaScript for bots gets content delivered; it does not restructure it. SiftServe rewrites each page's representation, keeps a human in the loop for every version, and serves the result from the edge, in your own Cloudflare account where you have one or on a supported CDN, with no changes to your origin.

Every page ships with a before-and-after audit score and per-page capture statistics, and the measurement methodology is public: fetching a document the way an agent does, with one raw HTTP GET and a crawler user-agent, no JavaScript, no rendering ("Fetch like an agent. One raw HTTP GET with a crawler user-agent. No JavaScript, no rendering: the document GPTBot or ClaudeBot receives."). The per-page numbers behind the token-reduction and readable-content figures ship in every pilot's audit report ("The per-page numbers behind both figures ship in every pilot's audit report."). The core commercial claim, that sifted pages earn about 20% more citations and AI referrals than their unsifted baseline, is stated as a hypothesis, before the data, and tested in every pilot: eight weeks, your traffic, before-and-after audit scores, and a report at week eight on which you decide whether to stay on.

We run our own site through the product. The siftserve.com homepage is served sifted to AI traffic, at 32 KB against a 368 KB original (a 91% reduction) with 96% coverage, and the three uncarried items were itemised at review. The homepage's review-desk screenshot is a real draft of siftserve.com, and the methodology post shows how to reproduce the sifted view yourself.

We handle data conservatively. The edge software records no visitor IP addresses and sets no cookies, dashboards show visitor data only in aggregate, and model providers are used through business APIs under terms that do not permit training on your content. The details are in our Terms of Service and Privacy Policy.

The people behind SiftServe.

The founder and the advisors, each named with what they built before, are on the team page. Rafi is an Engineering Leader turned founder with 17+ years of experience in architecting large-scale data and AI-driven systems, with a strong foundation in machine learning, personalization systems, and data platform engineering.

Where SiftServe operates from.

SiftServe is a product of NextON Consulting FZE, a UAE-based firm with over eight years of experience delivering data and research services to clients across 35+ countries. Our Terms of Service and Privacy Policy set out the customer agreement and how we handle data.

Talk to us.

Questions, pilots, or press: info@siftserve.com. SiftServe is also on LinkedIn and Facebook.