Matchmaking site — full SEO structural overhaul

A matchmaking service that needed its whole search visibility foundation tidied in one pass.

For matching services, what matters most is how you send a "trust" signal to both search engines and prospective users. People aren't just looking up information — they're handing over their time and personal details to a service. So trust signals like who operates the site, what the service covers, reviews, and contact information have to be clearly communicated to search engines before organic traffic shows up. Operationally this site was solid, but from the search engine's perspective it was sending almost none of those trust signals.

The initial diagnosis turned up problems across multiple areas, not just one. Meta information was missing or inconsistent page by page. Structured data that communicates business identity — Organization, LocalBusiness — had not been applied at all. The sitemap was several versions out of date, and robots.txt still wasn't blocking temporary pages. Search Console wasn't even registered. In effect, the search engine had never really inspected this site.

In situations like this, fixing one or two areas doesn't move the needle. Cleaning the meta alone doesn't help if the sitemap is broken and the indexer doesn't come in. Cleaning the sitemap alone doesn't help if the meta is missing and click-through rate stays flat. Cleaning both still doesn't help if Search Console isn't in place to measure the change. So we set the scope from the start as "rebuild the whole site's SEO foundation in one pass."

The work split into four areas, executed in sequence.

First, page-by-page meta cleanup. We rewrote titles, meta descriptions, and OG meta across the six core pages — home, service intro, matching process, pricing, reviews, and inquiry — using a unified template. Given the nature of a matching service, we mapped keywords like "blind date," "matching," and "relationship consulting" so each page owned the intent that fit its content.

Second, structured data. Organization JSON-LD carried the business info, phone number, address, and SNS links via sameAs, making the business entity explicit to search engines and AI. Matching services can also use Service schema, so we added service type, area served, and price range as structured data. The reviews page got Review and AggregateRating schema so star ratings become eligible to surface in search. We also added BreadcrumbList for navigation paths.

Third, indexing policy. We regenerated the sitemap against the latest page structure, and used robots.txt to block private areas — admin, draft, in-progress matching user pages. Canonical tags were set explicitly on every page to point at themselves, closing off duplicate indexing risk.

Fourth, Search Console registration, verification, and indexing requests. After domain verification, we submitted the sitemap and requested indexing for the main pages. From that point on, the client had an environment for monitoring indexing status and search visibility directly.

The directly verifiable changes were clear. Meta consistency was secured across the six core pages, four types of JSON-LD passed the validator, the sitemap correctly contained only public pages, and Search Console gave real-time visibility into the indexing progress. For a matching service — where "trust signal" is the single most important factor — this work laid the groundwork for the search engine to recognise the site as "a matching service operated by a verified business."

Matching services don't publish content frequently, so an SEO structure put in place once tends to compound for a long time. That makes one-pass cleanup work like this especially effective for this kind of business.