I co-founded HalloCasa — a global real estate broker directory with listings, profiles, subscriptions, and courses. Organic search should be a major channel for us. But when I sat down to build an SEO strategy, I did not want to spend a day clicking through dashboards, exporting CSVs, and stitching screenshots into a doc.

Instead I paired my AI Cursor with the SISTRIX MCP and ran a full audit in one agent session: multi-market visibility baseline, ranking URLs, keyword opportunities, competitor overlap, backlink profile — cross-referenced against our Next.js codebase for canonical tags, hreflang, and sitemaps. The output was a prioritized roadmap, not gut feel.

The whole thing started with one prompt:

Use the SISTRIX MCP to develop a sophisticated SEO strategy for https://hallocasa.com/

No keyword spreadsheets, no elaborate system prompt — just the domain and the tool. From there the agent pulled SISTRIX data market by market, read our repo, and turned it into a strategy doc with prioritized tiers.

This post is about that workflow: what SISTRIX and its MCP are, why MCP matters for SEO, and what the data actually told us about hallocasa.com.

---

What is SISTRIX?

SISTRIX is a German SEO platform widely used in the DACH market and beyond. Its headline metric is the Visibility Index (Sichtbarkeitsindex) — a score derived from ranking positions and search volume across all keywords a domain ranks for. You also get keyword rankings, backlink data, competitor overlap, search intent, and (newer) AI visibility tooling.

For a site like HalloCasa — global broker directory, LatAm-heavy country list, German expat content on the blog — SISTRIX is useful because you can slice by country (de, us, co, es, mx, …) and compare markets in one session instead of assuming one Google index fits all.

---

Why MCP for SEO tools?

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools through a unified interface. Without it, chatbots guess or hallucinate metrics. With it, they pull live data from your SEO platform.

Without MCP	With MCP
Tab-hopping, manual exports	Agent queries live data in conversation
Stale screenshots in strategy docs	Reproducible, dated API pulls
SEO analyst and developer in separate tools	Agent cross-references rankings and your repo

In Cursor → Settings → Tools & MCP, you wire the SISTRIX server once. The agent then calls tools like domain_visindex or keyword_domain_seo as part of normal chat — same as reading files or running terminal commands.

Workflow (Cursor + SISTRIX MCP + codebase):

Step	You	Agent
1	Ask for SEO audit of your domain	Calls SISTRIX MCP tools per market
2	Point agent at your repo	Reads seo.ts, MetaData.tsx, robots.txt, sitemaps
3	Ask for strategy + priorities	Synthesizes data + code findings into actionable doc

---

Setting up the SISTRIX MCP

SISTRIX ships an official MCP server. Docs and setup guides:

Resource	Link
Main hub	Connection to AI with MCP
OAuth for all plans (2025+)	SISTRIX MCP Servers changelog
Technical reference	Technical Information MCP
ChatGPT setup	Setting up ChatGPT
Claude setup	Setting up Claude

Endpoint: https://api.sistrix.com/mcp/

Auth: OAuth now works on all SISTRIX plans — log in, no API key required. API keys still work on Plus+ if you prefer. Per SISTRIX docs, MCP requests currently do not consume API credits (unlike direct API calls). For Cursor, configure the MCP server with the same endpoint plus OAuth or an API key in your MCP config.

---

SISTRIX MCP tool surface

The MCP exposes dozens of tools. In the HalloCasa audit we leaned on these groups:

Category	Example tools	What you learn
Domain visibility	domain_visindex, domain_kwcount_seo, domain_ranking_distribution	Footprint per market, page-1 keyword count
Keywords	keyword_domain_seo, domain_opportunities, keyword_seo_metrics	What ranks, near-wins, volume and intent
Competition	domain_competitors_seo, domain_ideas	Overlap and content gaps
Links	links_list	Toxic vs legitimate backlinks
AI visibility	ai_entity	AEO baseline (our HalloCasa entity call returned HTTP 500)
Projects	project_ranking, project_visibilityindex, …	Ongoing tracking once a project exists

Pass country as an ISO code (de, us, co, es, mx, …) to audit multiple markets in one session. That is how we discovered Germany has history while Colombia and Mexico have essentially zero visibility today.

---

HalloCasa case study: what the data showed

Domain: hallocasa.com. The agent pulled SISTRIX data across our main markets (DE, US, ES, CO, MX).

Baseline snapshot

Germany is the only market with meaningful organic history — visibility has declined sharply since a peak a few years ago. The US and Spain show traces of activity (mostly blog content). Colombia and Mexico, despite being core business geography, had essentially no organic footprint at all.

That mismatch between business focus and search visibility was the first big insight — and only visible because we queried per country instead of treating Google as one global index.

Where rankings actually live

Almost all SEO value sits on blog.hallocasa.com, mostly German articles about LatAm real estate (Chile, Colombia, Peru, Argentina, Mexico). The directory (www.hallocasa.com) barely ranks by comparison — a handful of broker-name profile queries and little else.

Headline finding: authority is stranded on a subdomain, not flowing to broker profiles and /brokers. That is a structural problem, not a content gap.

Near-win keywords (fastest ranking upside)

SISTRIX domain_opportunities surfaced several German keywords where we already rank on page 2 — cross-border investment and expat real estate topics with relatively low competition. Pushing those over the line to page 1 is lower effort than chasing new head terms.

Competitors (DE organic overlap)

The overlap set is a mix of large German property portals, international luxury listing sites, and niche expat/investment blogs. We are not competing on generic German portal head terms; our wedge is cross-border / expat investor content.

Backlinks: mostly noise

The link profile is dominated by SEO directory and PBN spam. Legitimate links exist but are sparse — partner podcasts, travel sites, conference media. Worth a GSC audit before any disavow; Google often ignores obvious spam automatically.

Code cross-check: why the directory does not rank

The agent read our Next.js repo alongside SISTRIX URLs. Technical issues that explain weak directory visibility:

• i18n via ?lang= on the directory, but canonical URLs strip the query — all nine locales collapse to one indexable URL per path.
• No hreflang anywhere; blog and home use path locales (/de/, /es/), apex uses query locales.
• Fragmented architecture: blog., home., and apex as separate properties; blog holds the rankings.

Fixing international SEO and consolidating blog authority onto the main domain are foundation work before scaling content in CO/MX.

---

Prioritized roadmap (90-day lens)

From the audit we tiered actions by effort vs impact:

P0 — do first (weeks 1–4)

Action	Why
GSC domain property + baseline KPIs	Cannot measure without it
www canonical + 301 all host variants	Stops split link equity
Blog → directory CTAs on top DE posts	Rankings exist; directory gets no traffic
Cross-link blog ↔ /brokers ↔ profiles	Partial authority transfer without migration

P1 — highest SEO upside (weeks 4–16)

Action	Why
Optimize near-win DE blog posts	Fastest ranking wins
Blog → /blog/ subfolder consolidation	Biggest structural lift for directory
Path locales + hreflang on apex	Required before ES/EN scale
DE pillar hub for cross-border investment	Captures commercial intent cluster

P3 — long bets

Spanish LatAm programmatic pages (CO/MX) only when broker inventory supports it — empty city templates would be thin-content risk.

---

How to replicate this workflow

1. Wire SISTRIX MCP in Cursor — endpoint https://api.sistrix.com/mcp/, setup docs, OAuth or API key.
2. Open with a clear ask — e.g. Use the SISTRIX MCP to develop a sophisticated SEO strategy for https://hallocasa.com/ (that was my entire starting prompt).
3. Ask for multi-market baseline — domain_visindex and domain_kwcount_seo per country.
4. Pull ranking URLs — keyword_domain_seo to see which subdomain or path actually ranks.
5. Pull opportunities, competitors, backlinks — domain_opportunities, domain_competitors_seo, links_list.
6. Audit your codebase — canonicals, hreflang, robots, sitemaps, i18n patterns.
7. Synthesize — strategy doc with prioritized tiers, not a data dump.

Sample deliverable: HalloCasa SEO strategy (PDF)

The agent session produced a full strategy document — baseline by market, competitor overlap, technical findings from our Next.js repo, and a P0–P3 roadmap. We exported it as PDF for stakeholders (pandoc + headless Chrome from the markdown in hallocasa-next/misc/seo).

Download PDF · View markdown source

Want something similar for your domain? I help teams run the same SISTRIX MCP + codebase audit workflow and turn it into a prioritized strategy doc like this. Reach out on LinkedIn.

---

Takeaways for other sites

• MCP turns SEO from dashboard archaeology into agent-native research. The agent pulls live SISTRIX data while you stay in the editor.
• Best results when the agent can read your repo too. Rankings tell you what ranks; code tells you why fixes are hard or easy.
• Multi-subdomain setups need an explicit architecture decision — consolidate (e.g. blog → /blog/) or cross-link heavily; do not assume authority transfers by default.
• Prioritize near-win keywords before greenfield programmatic SEO or nine-locale translation sprees.
• Match market data to business focus. We had almost no visibility in CO/MX despite LatAm being core geography — that mismatch only shows up when you query per country.

---

What is next for HalloCasa

This post is about the research method — but the audit gave us a clear roadmap, and I am excited to implement it: P0 fixes first, then the DE near-win posts and blog consolidation. SISTRIX will stay in the loop for ongoing tracking, not just this one-off session.

The same MCP setup opens GEO (Generative Engine Optimization): SISTRIX’s AI visibility tools (ai_entity, and related project tooling) let us baseline how HalloCasa shows up in AI answers and measure lift as we fix structure and content. Our first ai_entity call hit a 500 — worth retrying once the foundation work lands.

I am co-founder of HalloCasa and use MCP heavily elsewhere in my stack (see How I Use OpenClaw for another angle on agent tooling). If you want help wiring SISTRIX MCP in Cursor or running a similar audit on your domain, reach out on LinkedIn.

Thanks to Benedikt Rudolf at SISTRIX for taking the time to walk me through the MCP — that conversation kicked off this workflow.