Sphinx by Tasken · Private beta

Answer the questions AI search asks.

Before ChatGPT answers your clients' buyers, it runs its own searches. Sphinx finds the searches a client's site does not answer, updates the pages that miss and writes the ones that do not exist. Your team runs it for every client, rebranded as yours.

Modeled for ChatGPT, Claude and Google AI

ChatGPT
Claude
Google AI

Send us a client's domain.

We send back a page showing what AI engines search for that client's buyers and what Sphinx would build or fix.

Or start the free week

Question map

Illustrative example

Wise

Wise

International business payments

ChatGPT

  • Best way to pay contractors overseas?
    Createnew page
  • Can a business hold multiple currencies?
    Update/multi-currency
  • How do bulk international payments work?
    Update/bulk-payments

Claude

  • Wise Business or a traditional bank?
    Createnew page
  • How can remote teams control spending?
    No change
  • Does Wise connect to accounting software?
    Update/integrations

Google AI

  • What do international transfers cost?
    Update/pricing
  • Can one account receive USD, EUR and GBP?
    Update/multi-currency
  • Which documents open a business account?
    Createnew page

Every question gets one page owner and one next move.

Query fan-out

One question, many searches.

An AI engine does not answer from one search. It splits a buyer's question into several, reads what comes back, then writes the answer. Each search is a chance for a client's page to be read, or skipped.

Wise

Illustrative example

01 · Buyer question

What is the best way to pay contractors overseas?

02 · Searches the engines run

  • ChatGPTcheapest way to pay international contractors
  • Google AIWise Business vs bank for paying freelancers abroad
  • Claudemulti-currency account for overseas contractor payments

03 · The page for it

Create a page

Paying contractors overseas

No page on the site owns this yet, so it gets one.

In Sphinx these searches are modeled for each engine. It never reads a private prompt or an engine's query log.

The question map

See the questions a client's site does not own yet.

Pick a topic and read every connected question across the site: answered, partial, missing or split between two pages doing the same job.

Seeded sample workspace. Every question carries its page owner and the surfaces it was modeled for.

Tap the screenshot to read it full size.

Create or update

Decide the page. Then do the work.

A missing answer may need a new page. A partial one usually belongs in a page you already have. Both sit in one plan, so the work never loses the reason it started.

Create a page

Give a missing intent its own page

When the topic has a distinct job and would overload the page that exists.

Update a page

Add the answer where it belongs

When a page already owns the intent but leaves follow-up questions open.

Seeded sample workspace. An existing page sits in the same plan as a new one.

Tap the screenshot to read it full size.

After the decision

Approved work lands on a dated plan.

Each approved decision gets a slot and keeps its evidence, so the plan still knows why the page exists.

Seeded sample workspace. Approved decisions land on dated slots.

Tap the screenshot to read it full size.

The whole system

Four evidence sources become one coverage plan.

Your site and rules, Search Console, Google search data and competitor pages go in. A ranked plan comes out.

Evidence in

Your website and rules

Pages, links, audience and boundaries

Google Search Console

Queries, clicks and positions

Google search data

Demand and search results

Competitor pages

Pages and topic gaps

Sphinx

Coverage intelligence

Sphinx builds the question map

  1. Model likely AI-search questions
  2. Assign each question to one page
  3. Spot gaps, weak answers and overlap
  4. Rank the work with evidence

Plan out

One decision for every question

The evidence, the page owner and the next move stay on the same row.

Create a page

A gap needs its own page

Update a page

Strengthen the page that owns it

Merge overlap

Combine pages doing the same job

No change

Leave it alone when evidence says so

Then it loops

Approved work ships, the site is rescanned and the plan refreshes. Each run learns from the last.

The self-learning loop

It gets sharper every run.

Every call your team makes teaches Sphinx what fits that client's site. The next run starts from there.

  1. 01ResearchTopics, keywords, modeled AI questions and competitor gaps.
  2. 02You decideApprove a page, or dismiss it with a reason.
  3. 03Write and publishIn your voice. Anything below the quality bar waits for a person.
  4. 04TrackSearch Console follows every published page.
  5. 05RescanThe plan refreshes against what is live.

Rescan feeds the next round of research

What it remembers

  • Dismiss a topic as off-brand or wrong audience, and it stays out of future runs.
  • A rejected update stays rejected for 90 days.
  • A No change call keeps its reason, so the same idea does not come back.
  • Your writing rules and never-do list shape every draft.
  • Search Console data ranks which pages to improve next.
Your version, not a template

We customize it for you, then keep tuning it.

The free week is the full product on our shared instance. Subscribe and we build your own instance, rebranded as yours for every client, and run it for you: hosting, maintenance, upgrades and support included.

01

A person from day one

Someone from Tasken works through your brief, writing rules, Search Console and publishing with you.

02

Tuned as you go

Tell us what reads wrong. We adjust the prompts, rules and checks for your sites.

03

Rebranded as yours

Your name, logo and colours on it, for your team and your clients.

04

Built for your workflow

Need a new step, report or integration? We build it, quoted on a call.

What it will not claim

Three things it will not promise.

Better said here than found out on a call.

Modeled, never observed

Sphinx models likely questions for ChatGPT, Claude and Google AI, Gemini included. It never reads a private prompt or a platform query log.

Not every question

The map is a working set with its evidence shown, not the full universe of what somebody could ask.

No promised numbers

Sphinx decides pages and tracks what you publish. It cannot promise a ranking, a citation or a traffic number.

Who it is for

For agencies that run content for several clients.

SEO and content agencies

One decision process across every client site, run by your team and rebranded as yours.

Agencies adding GEO

Every GEO recommendation tied to one page and the modeled searches behind it.

Consultants with a few clients

The same process on each client site, with a person approving the call.

Questions about Sphinx

Ask the awkward ones.

The objections that come up first, answered from how the product works today.

Three things: the questions that client's buyers are likely to ask AI, the searches the engines run to answer them and what Sphinx would build or fix. It is private and not indexed.

Your team. Each client site is its own project with its own brief, rules and Search Console, inside an instance rebranded as yours. Your clients see the pages, not the tool, unless you choose to show them.

No. Keyword research hands you a list of terms. Sphinx starts from the questions people are likely to ask AI about your topic, and each one gets a single page owner and one move: create a page, update a page, merge overlap or no change. That is GEO, generative engine optimization, run as page decisions instead of a spreadsheet of terms.

No. Plenty of questions belong inside a page you already have, and some are better left alone. The decision is made per question, so a scan can end with more updates than new pages.

Your own OpenRouter API key, which the first screen checks. The week starts at your first sign-in, covers up to three client sites and needs no card. When it ends, nothing new runs, and everything you made stays readable.

A client site it can crawl, and about ten minutes to correct the brief it derives from the pages. Search Console is optional and makes the evidence stronger where it is connected. Competitor pages are public. Nothing writes to your CMS until you connect it. Once connected, approved pages publish on their own, or wait for a person if you set it that way.

It is recorded with its reason and stays on the question, so the same idea does not come back as a fresh recommendation after the next scan.

No. Sphinx by Tasken is Tasken's question-coverage product and has no connection to sphinx.ai.

While Sphinx is in private beta the price is shared on request: ask on the walkthrough call or when you send a client's domain. The free week costs nothing and needs no card.

Your client's page

Send us a client's domain. We send back the page.

The page shows what AI engines search for that client's buyers and what Sphinx would build or fix.

Or write to mudi@tasken.ai.

Rather try it yourself?

Try it free for a week. Plug in your OpenRouter API key and test everything on your own site. No card.

Start the free week
Sphinx walkthrough

Or book 30 minutes with Mudi.

On one of your client sites. We run Sphinx on it before the call, so the 30 minutes go on its pages.

Calendar not loading? Open it in a new tab.