How I built a bilingual site that ranks in Google and AI answers

Rajasthan's SSO portal is one login for dozens of state services, used by millions of people. The official help is hard to follow, so people search for the basics: how to register, how to log in, how to recover a locked account. I built rajssoidguide.in to answer those questions clearly, in both English and Hindi.

The content was the easy part. The real work was getting a small site to show up against portals with far more authority. Here is what actually moved the needle.

Bilingual is a ranking problem, not just a translation one

If you publish the same guide in two languages without telling search engines how the versions relate, they compete with each other and both suffer. hreflang fixes that. In the Next.js App Router it lives in the metadata:

​

export const metadata = {
  alternates: {
    canonical: "https://rajssoidguide.in/sso-login",
    languages: {
      "en-IN": "https://rajssoidguide.in/en/sso-login",
      "hi-IN": "https://rajssoidguide.in/hi/sso-login",
    },
  },
};
​```



Now Google serves the Hindi page to Hindi searchers and the English page to everyone else, instead of guessing.

## Schema is what gets you into AI answers

FAQ and HowTo structured data turns a page into something Google and AI assistants can quote directly. Every guide carries a FAQPage block:

​

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How do I create a Rajasthan SSO ID?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Go to sso.rajasthan.gov.in, choose Registration, pick Citizen, and verify with your Jan Aadhaar or Google account."
    }
  }]
}
​```



## Write the answer for the quote

AI answers and featured snippets pull the first clear sentence that answers the question. So each page leads with a direct 40 to 60 word answer, then the detail below. Bury the answer three paragraphs down and you lose the citation to a site that put it up top.

## Find gaps instead of guessing

Instead of writing what I assumed people wanted, I looked at which specific questions the big portals answered poorly, then wrote those. Underserved, high-intent queries are far easier to rank for than broad ones.

## Takeaways

You do not need a big domain to win these queries. A small site with clear answers and correct markup can beat authority on the right questions. For anyone building info or docs sites: get hreflang right, add FAQ/HowTo schema, and put the answer in the first two lines.

Built with Next.js and Tailwind. I write about shipping real products at [devxkamlesh.com](https://devxkamlesh.com).

*Have you tried optimizing content for AI answers yet? What worked or didn't for you? I'd like to hear in the comments.*