{"slug": "developers-are-optimising-for-google-ai-is-watching-something-else", "title": "Developers Are Optimising for Google. AI Is Watching Something Else", "summary": "A developer rebuilding their portfolio discovered that AI systems evaluate websites based on structured meaning rather than visual design or search rankings. Technologies like Schema.org and entity-based understanding are becoming critical as AI assistants prioritize context and trustworthiness over keyword matching.", "body_md": "**\n\n**\n\nAI isn't replacing SEO.It's changing what it means to build a website that's truly understandable.\n\nFor years, developers have built websites with two audiences in mind:\n\nToday, there's a third audience we can no longer ignore.\n\n**🤖 AI Systems.**\n\nAs AI assistants become a common way to discover information, websites are no longer judged only by how they look or where they rank.\n\nThey're increasingly evaluated by how well they communicate meaning.\n\nThat shift changes how we should think about web development.\n\nOver the past few weeks, I've been rebuilding and optimising my personal portfolio.\n\nLike many developers, I started with familiar priorities:\n\nBut while implementing features like Schema.org structured data, Open Graph metadata, canonical URLs, XML sitemaps, and author information, I noticed something interesting.\n\nNone of those improvements were primarily for visitors.\n\nMost users would never even know they existed.\n\nYet they dramatically changed how machines understood my website.\n\nThat made me realise something.\n\nWe're entering a web where discoverability isn't only about search engines anymore.\n\nIt's increasingly about helping AI understand context.\n\nSearch engines traditionally answer one question:\n\nWhich pages are most relevant?\n\nLarge Language Models attempt to answer another:\n\nWhich information is trustworthy enough to explain?\n\nThose questions sound similar.\n\nThey aren't.\n\nTraditional search focuses on retrieval.\n\nAI focuses on understanding.\n\n```\nUser Question\n      │\n      ▼\n Search Engine\n      │\nFind Relevant Pages\n      │\n      ▼\n Click Result\n\nUser Question\n      │\n      ▼\n AI Assistant\n      │\nUnderstands Context\nEvaluates Relationships\nSummarises Information\n      │\n      ▼\nGenerated Response\n```\n\nRanking is only part of the second process.\n\nUnderstanding becomes the real challenge.\n\nWhen people visit your portfolio, they instantly recognise:\n\nAI doesn't experience your website that way.\n\nInstead, it builds relationships.\n\n```\nRajshree\n      │\n      ├── Software Engineer\n      ├── MERN Stack Developer\n      ├── AI & ML\n      ├── Portfolio\n      ├── GitHub\n      ├── LinkedIn\n      ├── Medium\n      └── Technical Articles\n```\n\nThe stronger and more consistent these relationships become across platforms, the easier it is for machines to understand your professional identity.\n\nThat's one reason why consistency matters far beyond branding.\n\nThink about where your professional identity exists today.\n\nEvery platform tells a small part of your story.\n\nWhen those stories align, search engines—and increasingly AI systems—gain confidence in understanding **who you are**.\n\nWhen they don't, ambiguity increases.\n\nThat's exactly why technologies like **Schema.org** have become so valuable.\n\nHere's a simple example.\n\n```\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"Person\",\n  \"name\": \"Rajshree\",\n  \"jobTitle\": \"Software Engineer\",\n  \"url\": \"https://rjshree.com\",\n  \"sameAs\": [\n    \"https://github.com/itsrjshree\",\n    \"https://linkedin.com/in/rjshree\",\n    \"https://dev.to/rjshree\",\n    \"https://rjshree.hashnode.dev\"\n  ]\n}\n```\n\nVisitors will never notice this.\n\nBut machines will.\n\nThis small piece of structured data answers several important questions instantly.\n\nThat isn't just SEO.\n\nThat's communication.\n\nFor years, SEO conversations revolved around keywords.\n\nDevelopers asked questions like:\n\nWhich keyword should I target?\n\nToday, another concept has become increasingly important:\n\nAn entity is something uniquely identifiable.\n\nExamples include:\n\nNotice something.\n\nThose aren't merely words.\n\nThey're concepts with relationships.\n\nInstead of matching keywords, AI attempts to connect knowledge.\n\n```\nRajshree\n     │\n     ├── Profession → Software Engineer\n     ├── Skills → MERN Stack\n     ├── Skills → AI & ML\n     ├── Website → rjshree.com\n     ├── Writes → Technical Articles\n     └── Builds → Web Applications\n```\n\nThat's a much richer understanding than simply counting keyword occurrences.\n\nWhen developers showcase a portfolio, the focus usually stays on what users can see.\n\nThose certainly improve user experience.\n\nBut another layer quietly powers modern discoverability.\n\n```\nModern Website\n\nVisible Layer\n──────────────\n✔ UI\n✔ Images\n✔ Typography\n✔ Animations\n✔ Content\n\nInvisible Layer\n──────────────\n✔ Structured Data\n✔ Metadata\n✔ Open Graph\n✔ robots.txt\n✔ XML Sitemap\n✔ Canonical URLs\n✔ Semantic HTML\n✔ Performance Signals\n✔ Author Identity\n```\n\nIronically, AI spends far more time analysing the invisible layer than admiring your animations.\n\nA beautiful portfolio with poor structure is like a beautifully designed book without a title, author, or table of contents.\n\nPeople may still appreciate it.\n\nMachines struggle to understand it.\n\nWhile rebuilding **rjshree.com**, I realised that most improvements I made weren't visual.\n\nVisitors probably wouldn't notice when I:\n\n`sameAs`\n\n,Yet these changes significantly improved how machines could interpret my website.\n\nThat experience completely changed how I think about modern web development.\n\nBuilding a website isn't only about designing interfaces anymore.\n\nIt's also about communicating information clearly—to humans, search engines, and increasingly, AI systems.\n\nAbsolutely not.\n\nGood SEO has always been about reducing ambiguity.\n\nEvery technical decision answers questions that machines would otherwise have to guess.\n\nA title tag answers:\n\nWhat is this page about?\n\nA canonical URL answers:\n\nWhich version is the original?\n\nSchema.org answers:\n\nWho created this content?\n\nA sitemap answers:\n\nWhich pages exist?\n\nSemantic HTML answers:\n\nHow is this information organised?\n\nNone of these practices became obsolete because AI arrived.\n\nIn fact, they're becoming even more valuable.\n\nBecause AI depends on structured, well-organised information to understand websites accurately.\n\nBacklinks still matter.\n\nThey always will.\n\nBut they're no longer the entire story.\n\nImagine discovering the same developer through:\n\nEvery platform reinforces the same identity.\n\nThe same expertise.\n\nThe same projects.\n\nThe same writing style.\n\nThe same technical interests.\n\nThat consistency becomes a trust signal—not only for people, but increasingly for machines as well.\n\nAuthority is no longer built through a single website.\n\nIt's built across an ecosystem.\n\nMany developers think of a portfolio as the final destination.\n\nIn reality, it should become the centre of your digital identity.\n\n```\n                  Personal Website\n                         │\n        ┌────────────────┼────────────────┐\n        │                │                │\n        ▼                ▼                ▼\n    GitHub          LinkedIn         Technical Blog\n                                         │\n                           ┌─────────────┴─────────────┐\n                           ▼                           ▼\n                        Dev.to                    Hashnode\n                           │\n                           ▼\n                           X / Social Platforms\n```\n\nEach platform strengthens the others.\n\nYour articles reference your portfolio.\n\nYour portfolio references your GitHub.\n\nYour GitHub links back to your website.\n\nYour LinkedIn showcases your writing.\n\nInstead of isolated profiles, you create a connected ecosystem.\n\nThat's how digital authority compounds over time.\n\nYou don't need a massive redesign.\n\nSmall improvements can make a meaningful difference.\n\n`sameAs`\n\nThese changes may not transform your UI.\n\nBut they dramatically improve how your website is understood.\n\nMany developers spend weeks perfecting visual effects.\n\n✨ Glassmorphism\n\n✨ Animated backgrounds\n\n✨ 3D models\n\n✨ Fancy transitions\n\nThere's nothing wrong with those.\n\nBut after opening dozens of portfolios, one question often remains unanswered.\n\n\"What exactly does this person do?\"\n\nThat's not a design problem.\n\nIt's a communication problem.\n\nThe best websites don't impress because they're complicated.\n\nThey impress because they're clear.\n\nVisitors—and machines—should understand your expertise within seconds.\n\nThe web has always evolved.\n\nWe moved from static HTML pages…\n\nto responsive websites…\n\nto mobile-first design…\n\nto performance optimisation…\n\nto technical SEO…\n\nNow we're entering another transition.\n\nOne centred around **understanding**.\n\nThe websites that thrive in the coming years won't simply be the fastest or the most visually impressive.\n\nThey'll be the ones that communicate clearly.\n\nTo users.\n\nTo search engines.\n\nAnd increasingly…\n\nTo AI.\n\n```\n                 Great Website\n\n             👤 Human Friendly\n                     +\n          🔎 Search Engine Friendly\n                     +\n             🤖 AI Understandable\n\n               = Future Ready\n```\n\nTechnology will continue to evolve.\n\nFrameworks will change.\n\nSearch algorithms will improve.\n\nAI models will become more capable.\n\nBut one principle is unlikely to change:\n\nBuild websites that are easy to understand—not just easy to find.\n\nHi, I'm **Rajshree**, a Software Engineer passionate about building modern web applications with the MERN stack while exploring AI, machine learning, technical SEO, and web performance.\n\nI enjoy building projects, writing about emerging technologies, and sharing practical insights that help developers build for the future.\n\n🌐 **Portfolio:** [https://rjshree.com](https://rjshree.com)\n\n💼 **LinkedIn:** [https://linkedin.com/in/rjshree](https://linkedin.com/in/rjshree)\n\n💻 **GitHub:** [https://github.com/itsrjshree](https://github.com/itsrjshree)\n\nIf you found this article useful, I'd love to hear your thoughts in the comments. What role do you think AI will play in the future of web discoverability?\n\nIf you enjoyed this article, let's connect and continue the conversation about modern web development, technical SEO, AI, and building a future-ready web.", "url": "https://wpnews.pro/news/developers-are-optimising-for-google-ai-is-watching-something-else", "canonical_source": "https://dev.to/rjshree/developers-are-optimising-for-google-ai-is-watching-something-else-dnf", "published_at": "2026-07-26 13:30:26+00:00", "updated_at": "2026-07-26 14:30:35.480881+00:00", "lang": "en", "topics": ["artificial-intelligence", "developer-tools", "ai-tools"], "entities": ["Rajshree", "Schema.org", "Google", "GitHub", "LinkedIn", "Medium", "Dev.to", "Hashnode"], "alternates": {"html": "https://wpnews.pro/news/developers-are-optimising-for-google-ai-is-watching-something-else", "markdown": "https://wpnews.pro/news/developers-are-optimising-for-google-ai-is-watching-something-else.md", "text": "https://wpnews.pro/news/developers-are-optimising-for-google-ai-is-watching-something-else.txt", "jsonld": "https://wpnews.pro/news/developers-are-optimising-for-google-ai-is-watching-something-else.jsonld"}}