Before we run the audit, we need to make sure we're asking the right questions about the right competitors to the right buyers. This document presents what we've learned about Lemkin Realty's market — your job is to tell us what we got right, what we got wrong, and what we missed.
Before we measure citation visibility in the Beit Shemesh / RBS Anglo real-estate space, these three signals tell us whether AI crawlers can reach, date, and trust your site's inventory. They're derived mechanically from the Layer 1 scan — no interpretation yet.
Anglo olim and overseas buyers are increasingly starting their "where should I buy in Israel" research inside AI assistants rather than working a phone list of agents — and in a market with no centralized MLS, the assistant's answer is the shortlist. For a boutique English-speaking agency in Beit Shemesh, being the name an AI names when a family asks "which agent should I use to buy in Ramat Beit Shemesh" is a first-mover advantage that compounds: early citations teach the platforms to trust your domain before larger national brands optimize for it.
This Foundation Review lays out the inputs that will drive your audit so we can validate them together before anything runs. It covers the competitive set that shapes head-to-head query construction, the buyer personas that determine which search intents we simulate, the capability and pain-point taxonomy that phrases those queries in real buyer language, and the Layer 1 technical baseline that determines whether AI platforms can access your content in the first place. Everything here is a proposal for you to confirm or correct — not a finished conclusion.
The validation call is a working session with real stakes. Two kinds of decisions come out of it: input validation — are the right buyers and competitors in the right tiers, given that several were inferred from the market rather than confirmed from your deals — and engineering triage — which technical fixes your team can start immediately, before results come back. The specific items for each are in the Pre-Call Checklist near the end.
Purpose This is the foundation for your GEO (Generative Engine Optimization) audit in the boutique Anglo real-estate space. We've assembled a knowledge graph — your competitors, buyers, capabilities, and buyer frustrations — plus a technical scan of aliyahrealty.com. The audit will then measure how AI assistants represent Lemkin Realty when Anglo buyers ask about buying, selling, and managing property in Beit Shemesh.
Your Job Read critically and mark what's wrong. Everywhere you see a purple question, we're genuinely uncertain and your answer changes how the audit runs. You know your buyers and your rivals better than any scan does — correct us.
Confidence Badges Each item carries a confidence level. High means directly sourced from your site or clear market signal. Medium means inferred or partially sourced — these are the ones we most want you to confirm. Treat every medium badge as an open question.
→ Validate Your site resolves at aliyahrealty.com, the brand reads as Lemkin Realty, and lemkinrealty.com also exists — three names for one firm. Which do buyers actually type and say to an assistant: "Lemkin Realty," "Aliyah Realty," or "Barbara Lemkin"? The canonical choice sets which entity we track for citations and which name variants we score AI answers against; pick the wrong anchor and we under-count mentions that land on a variant.
5 personas: 3 decision-makers, 1 evaluator, 1 influencer — the buyer archetypes that drive which Anglo real-estate searches we simulate in the audit.
Critical Review Area Personas are the single highest-leverage input — every simulated query is written in one of these buyers' voices. Two of the five (Michael Katz and Jonathan Weiss) were inferred from the Israeli Anglo property market rather than confirmed from your actual client list. If a persona isn't real, every query we spend in that voice is wasted.
Data Sourcing Note Names, roles, and influence levels come from the knowledge graph (site content and market signal). Because this is a consumer agency, the B2B "seniority / department / veto" fields are mapped onto household and investor buying roles — e.g., "decision-maker" means the person who signs the purchase, not a corporate title. Buying jobs and query focus areas are synthesized from each persona's role and the pain points linked to it.
→ Does David typically engage before aliyah (searching from abroad, neighborhood-first) or after landing (already in Israel, home-first)? If pre-aliyah dominates, we weight his query set toward relocation and community-fit intents rather than active listing searches.
→ Do overseas investors actually make up a meaningful share of your deals, or is your book really relocating families and local sellers? If investors are rare, we cut the investment/yield query cluster and reallocate that budget to family and seller searches.
→ Sara is tagged "evaluator" without veto — but a move-up seller usually controls the listing decision and the next purchase. Is she really a joint decision-maker? If she holds veto, we promote her to decision-maker and run a full seller-side query cluster (marketing, exposure, pricing), not just buyer intents.
→ Jonathan and Michael Katz are both inferred diaspora buyers who purchase remotely — does the second-home buyer behave distinctly from the investor, or do they search the same way? If they overlap, we merge them into one diaspora cluster and free the budget for a confirmed local persona.
→ Is property management an acquisition channel (owners find Lemkin to manage, then later buy or sell through you) or a retention service you add after a sale? If it's a real front door, management queries earn their own cluster; if it's an add-on, they fold into the investor's journey.
→ Missing Personas? These roles sometimes show up in Beit Shemesh Anglo deals — do they show up in yours? (1) Native-Israeli / Hebrew-speaking buyer or seller — do non-Anglo clients transact with you enough to warrant Hebrew-intent queries? (2) Chutznik parent buying for a child making aliyah alone or in yeshiva/seminary — a distinct "buying on behalf of" motion. (3) First-time young dati-leumi couple buying a starter apartment in RBS — price-sensitive, community-driven, different from the relocating family. Who else keeps showing up in your deals?
5 primary + 4 secondary competitors identified across the Beit Shemesh / RBS and national Anglo real-estate market.
Why Tiers Matter Tier assignment decides which rivals get head-to-head queries — each primary competitor draws roughly 5–8 direct-comparison prompts (e.g., "Lemkin Realty vs Mordy Real Estate for buying in RBS" or "best English-speaking agent in Beit Shemesh"), so five primaries account for ~30–40 of the audit's competitive queries. We're least certain about Anglo-Saxon Real Estate, listed primary at medium confidence — if that national franchise rarely appears in your actual deals, moving it to secondary shifts roughly 6–8 queries off it and onto a truer local rival.
→ Validate Three questions on this set: (1) Tier accuracy — do you actually win or lose deals against the national Anglo firms (Tivuch Shelly, Anglo-Saxon at medium confidence), or is your real competition the other RBS agents (Mordy, Elite, Yigal)? If the nationals don't appear in your deals, we move them to secondary and redirect ~12–16 head-to-head queries. (2) Missing rivals — which local Beit Shemesh agent or agency do you lose to most that isn't listed here? (3) Irrelevant — are the portals / DIY players (Israel Property Hub, Janglo) real competitors for your buyers, or noise we should drop?
12 buyer-level capabilities mapped — these determine which capability queries the audit tests in the Anglo RBS real-estate space.
Show me what's actually available in Ramat Beit Shemesh right now, including the listings I can't find on the big sites.
I need an agent who speaks my language and gets what an American / British family is looking for in a community.
Help me pick the right neighborhood for my family's religious level, schools, and community before I even look at apartments.
I want to buy off-plan in a new RBS project — walk me through the developer, the specs, and the timeline.
How do I know this agent is honest and actually known in Beit Shemesh, not going to take advantage of an outsider?
Make sure I'm not overpaying and that someone is actually on my side when we negotiate the price.
Get my home in front of the right buyers with good photos, video, and open houses so I get the best price.
I need someone to connect me with an English-speaking lawyer and mortgage broker and shepherd the paperwork to closing.
I'm buying from abroad and can't fly in for every viewing — can you do video tours and help me buy remotely?
I own an apartment in Israel but live abroad — manage the tenants, rent collection, and maintenance for me.
Can you also help me look in Jerusalem, Netanya, or Tel Aviv, or are you really just a Beit Shemesh agency?
I want to browse a clean, searchable, up-to-date listings site with filters and prices instead of calling five agents.
Prioritize Your Strengths Five capabilities are rated Strong — the audit tests all twelve, but competitive-differentiation queries will emphasize three. Which of these best represents where Lemkin Realty actually wins deals?
• Beit Shemesh / RBS Local Inventory & Off-Market Access
• English-Speaking, Culturally-Fluent Service for Anglos
• Aliyah & Relocation Consulting
• New Construction & Pre-Construction (Kablan) Sales
• Reputation, Track Record & Trust
→ Validate (1) Rating accuracy — "Buyer Representation & Price Negotiation" and "Remote / Overseas Buyer Support" are rated moderate on inference, not evidence; against Mordy or Tivuch Shelly, are these where you win or where you lose? (2) Undersold weak spots — we rated "Coverage Beyond Beit Shemesh" and "Online Listings UX" weak because you read as an RBS specialist without a portal-grade site — is that a true gap, or do you quietly handle Jerusalem / Tel Aviv and run a real search platform? Misjudge either and we test the wrong differentiation queries. (3) Merge / drop — is any capability here something you don't really sell, so we shouldn't test it at all?
11 pain points: 6 high, 5 medium severity — the buyer frustrations whose language becomes how the audit's queries are phrased.
→ Validate (1) Severity — six pains are rated high, and all four "buying" pains (no-MLS, Hebrew contracts, overpaying, remote buying) hit three personas each; is that the real hierarchy, or does one dominate every deal? (2) Buyer language — do these phrasings match how your clients actually complain to you, or are they market-generic (they weren't mined from Lemkin's own reviews)? (3) Missing pains — these commonly surface in RBS Anglo deals — do yours? Arnona / carrying-cost surprises after purchase; illiquidity and trouble reselling later in a thin market; construction noise & long-term neighborhood trajectory in fast-developing RBS. What's the frustration you hear most that isn't here?
These are the technical findings from our scan of aliyahrealty.com. They determine whether AI crawlers can access and trust your content — engineering can act on them now, independent of the validation call.
Engineering — Start Immediately The good news: robots.txt gives every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) full access — nothing is blocked. The bad news: two conversion- and discovery-critical faults are live right now. (1) The entire /location/ neighborhood taxonomy (~193 URLs) returns HTTP 500 — the exact pages that would answer "homes for sale in Ramat Beit Shemesh Aleph." (2) Primary nav and footer CTAs point to site.aliyahrealty.com, a host that doesn't resolve, orphaning key destinations. Both should go to engineering today; a third fix (stale/missing dates on commercial pages) can follow.
What we found: All URLs under /location/ return HTTP 500 (Internal Server Error), confirmed server-side with an independent HTTP client and reproduced with a Googlebot user-agent, so live crawlers hit the same error. location-sitemap.xml advertises 193 of these URLs (e.g. /location/ramat-beit-shemesh-a/, /location/dolev/, /location/jerusalem-2/, /location/tel-aviv/). Core pages, /realty/ listings, /new-project/ pages, and blog posts all return HTTP 200.
Why it matters: The /location/ taxonomy is the neighborhood-level browsing layer — exactly the pages that answer high-intent queries like "homes for sale in Ramat Beit Shemesh Aleph" and get surfaced by AI assistants. With every one of these ~193 pages erroring, AI crawlers can index none of Lemkin's neighborhood inventory, and the errors are actively advertised in the sitemap, wasting crawl budget and signalling a broken site.
Recommended fix: Diagnose and fix the server error on the /location/ taxonomy template (likely a WordPress/theme template or plugin fault, since sibling taxonomies like /realty/ and /new-project/ render fine). Verify a sample of location URLs returns 200 with rendered content, then confirm re-crawlability. If any location URLs are intentionally retired, return 404/410 and remove them from location-sitemap.xml rather than leaving 500s.
What we found: Numerous navigation, button, and footer links on the rendered homepage point to https://site.aliyahrealty.com/ rather than the canonical https://aliyahrealty.com/. That host does not resolve — DNS lookup returns ENOTFOUND via two independent tools. Affected links include the "Home" nav item, the "Sell With Us" and "View All Properties for Sale/Rent" CTAs, "Property Management," "Buy a Home," "Contact Us," and the Terms & Conditions / Privacy Policy footer links.
Why it matters: These are conversion-critical internal links (including the primary seller CTA). Because the target host doesn't resolve, both users and AI/search crawlers following them hit a dead end, and the key destination pages are partially orphaned from the internal link graph crawlers use to discover and weight content. Split references between two hostnames also create canonical/duplicate-host ambiguity.
Recommended fix: Update all internal links to use the canonical https://aliyahrealty.com host (or, if site.aliyahrealty.com is meant to exist, add the DNS record and 301-redirect it to the apex). Audit the theme/menu configuration and any hard-coded base URLs so newly generated links use the live domain, and re-test that every primary nav/footer link resolves to 200.
What we found: Sitemap lastmod values on core commercial pages are stale and contradicted by live content: the homepage lastmod is 2025-07-01 yet it links blog posts published June 2026; /for-sale/ lastmod is 2025-02-05 though it renders current 2026 listings; /new-project/ detail pages carry January-2025 lastmods. None of the commercial/product pages (home, for-sale, for-rent, properties, new-projects, /realty/ listings, /new-project/ pages) expose a visible published or updated date. Blog posts, by contrast, show reliable visible dates.
Why it matters: AI assistants — ChatGPT in particular — concentrate citations on content they can confirm is recent (ConvertMate found 76.4% of ChatGPT's most-cited pages were updated within 30 days; Ahrefs found AI-cited content is ~25.7% fresher on average). When the only machine-readable freshness signal (sitemap lastmod) is stale/wrong and no on-page date exists, crawlers can't credit these commercial pages with recency, and the wrong timestamps undermine trust in the sitemap as a whole.
Recommended fix: Fix the sitemap generator so lastmod reflects genuine last-modified time (Yoast normally does this — investigate why core pages are frozen at 2025 dates). Add visible "last updated" dates to commercial/service pages, and refresh the stale /new-project/ pages that still describe developments as "new."
What we found: Several commercially important pages lack a single clear H1 and lead with an H2 or generic template headings. /for-sale/, /properties/, /new-projects/, and the /new-project/ detail pages begin at H2 with no H1; individual /realty/ listing pages use the property title as the only substantive heading, surrounded by repeated template labels ("Get in touch for more details," "Property Location," "Share This Property"). Blog posts, by contrast, have exemplary single-H1 + descriptive-H2 structure.
Why it matters: A clear, descriptive heading hierarchy is how LLMs segment a page into citable passages and identify its primary topic. Pages that open at H2 or whose headings are boilerplate labels give crawlers no strong topical anchor, lowering the odds the neighborhood/inventory content is extracted and cited.
Recommended fix: Ensure every commercial page emits exactly one descriptive H1 (e.g. "Homes for Sale in Ramat Beit Shemesh" on /for-sale/, the property title as H1 on listing pages) and that section labels use a logical H2/H3 order rather than styling-only headings. This is largely a theme-template change.
What we found: The /realty/ listing template auto-generates only 20–90 words of descriptive prose per property (several under 45 words) surrounded by spec icons and photo galleries, and the core listing hubs (/for-sale/, /for-rent/, /properties/, /new-projects/) render as image-driven grids with little standalone text. Measured content depth for these pages sits at 0.3–0.4, at or below the thin-content threshold.
Why it matters: Image-heavy pages with almost no extractable prose give an LLM little to quote when answering a buyer's question, so even correctly-crawled inventory contributes weakly to AI answers. This is a systemic template characteristic (every listing is generated the same way) rather than a one-off editorial choice, which is why it's flagged as a structural signal-quality issue; the prioritization of which specific pages to enrich is left to the full audit.
Recommended fix: Adjust the listing template to encourage/require a fuller descriptive paragraph (location context, layout, neighborhood fit) and add a short descriptive intro block to each listing hub. Aim for self-contained passages a crawler can extract.
The following items could not be assessed through our analysis method (rendered markdown). We recommend your engineering team verify these manually before the validation call.
What to check: Our analysis reads rendered page content, so JSON-LD / schema.org blocks in the <head> aren't visible to us. The site runs WordPress with Yoast SEO (which usually emits some Organization/WebPage schema), but the most valuable types — RealEstateListing/Product on listings, FAQPage on the Q&A blog posts, BreadcrumbList — are unconfirmed.
Recommended action: Verify with Google's Rich Results Test or the Schema Markup Validator on a listing page, a blog FAQ page, and the homepage. Add RealEstateListing/Product schema to /realty/ pages and FAQPage schema to the Q&A blog posts where missing.
What to check: Meta description and Open Graph/social tags live in the HTML <head> and aren't present in rendered-markdown output, so we couldn't confirm their presence or quality. On a Yoast site they're usually present but may be auto-generated or missing on the thin listing pages.
Recommended action: Spot-check meta descriptions and OG tags with view-source or an SEO/social-preview crawler (e.g. Screaming Frog) across a homepage, a listing page, and a blog post; ensure listing and location pages have unique, descriptive meta descriptions.
What to check: We can't directly detect client-side rendering from rendered-markdown output. As a positive indirect signal, every HTTP 200 page we fetched returned substantial server-rendered text, which is consistent with a server-rendered WordPress site and argues against a CSR-blocking problem. The /location/ 500s are a separate server issue, not CSR.
Recommended action: Confirm by loading a listing page and a blog post with JavaScript disabled (or via the URL Inspection tool) and checking the core content is present in the raw HTML.
Partial Sample This scan covered 34 pages, a small slice of a site whose sitemaps advertise 193 location URLs and roughly 1,900 /realty/ listings. Freshness could only be scored on the 8 blog pages — the 24 commercial pages and 2 structural pages carry no detectable date, and schema coverage couldn't be assessed on any page. Treat the summary scores as directional; the manual verification items above close the biggest blind spots.
Why Now GEO in local Anglo real estate is still early-innings — you're competing against inaction, not entrenched strategies.
• Anglo olim and overseas buyers are shifting their "where and who should I buy through" research into AI assistants quarter over quarter.
• Early citations compound: assistants learn to trust domains they already cite, so the agency that shows up first keeps showing up.
• In a no-MLS market, the assistant's answer is the shortlist — being the named agent is disproportionately valuable.
• The Beit Shemesh Anglo niche is small enough that a boutique firm can realistically own it before a national brand optimizes for it.
The full audit will measure how AI assistants actually answer Anglo buyer queries in the RBS market — from "best English-speaking real estate agent in Beit Shemesh" and "which RBS neighborhood fits a religious Anglo family" to "how much can a foreigner borrow to buy in Israel" and "buying a Beit Shemesh apartment from abroad." You'll see exactly which of these return your competitors (Mordy, Elite, Yigal, Tivuch Shelly) but not Lemkin — and what it would take to appear in them. Fixing the Layer 1 issues now means the audit measures your baseline after the neighborhood pages come back online, not while they're returning 500s.
45–60 minutes to walk through this document together, confirm the personas and competitors, and settle the open questions in the checklist below.
We generate buyer queries from the validated knowledge graph and run them across the selected AI platforms in your buyers' real language.
Visibility analysis, competitive positioning, and a three-layer action plan showing where you're cited, where you're absent, and what to fix first.
Start Now — Engineering Three technical fixes don't depend on the rest of the audit and will improve your baseline visibility before we even measure it: (1) repair the /location/ HTTP 500 so all ~193 neighborhood pages return 200 and become crawlable; (2) repoint the dead site.aliyahrealty.com nav/footer/CTA links to the canonical aliyahrealty.com; (3) fix the stale sitemap lastmod dates and add visible "last updated" dates to commercial pages. Note: crawler access is already confirmed open — robots.txt allows every major AI bot — so these fixes translate directly into crawlable, dateable content.
Two jobs before we meet. The questions on the left require your judgment — no one knows your business better than you. The engineering tasks on the right don't require the call at all.