My Portfolio Failed Google’s AI-Readiness Test — Here’s the Checklist I Built to Fix It
I run a full-stack and AI developer portfolio. It has clean metadata, Open Graph tags, verified Google Search Console and Bing Webmaster Tools accounts, optimized images, and a solid technical foundation. On paper, it looked like a well-optimized website.
Then I decided to look at it from a different perspective.
Instead of viewing it as a visitor, I fetched my own blog page the same way a crawler or an AI search engine might — without executing JavaScript.
The result surprised me.
The page title was there. The meta description loaded correctly. The navigation appeared as expected.
But under “Technical Blog & Articles,” there were no blog posts.
No article titles.
No publication dates.
No content.
Just a placeholder telling users that JavaScript was required to render the page.
Every article I’d written was invisible to anything that relied on the raw HTML response. That includes many AI crawlers, social preview bots, and, depending on how they retrieve information, some of the systems powering AI experiences like ChatGPT, Gemini, and Perplexity.
That realization completely changed how I think about modern SEO.
This isn’t about adding another keyword or installing an llms.txt file.
It’s about making sure your content can actually be discovered, understood, and referenced by the systems that increasingly sit between your website and your audience.
Traditional SEO Still Matters, But It Isn’t the Whole Story
Google has made it clear that there isn’t a separate “AI ranking algorithm.” The same fundamentals that help websites succeed in traditional search crawlability, helpful content, structured information, and technical qualityalso support visibility in AI-powered search experiences.
What has changed is how information is consumed.
Traditional search usually follows a simple path:
Rank → Show a link → User clicks
AI-powered search works differently:
Retrieve → Compare trusted sources → Generate an answer → Cite sources (sometimes) → User may never visit the website
That changes the goal.
Instead of optimizing only for rankings, developers now need to think about retrieval, clarity, and machine-readable content.
If an AI system can’t understand your page, it can’t reference it.
How AI Search Retrieves Information
Most modern AI search systems follow a retrieval-based workflow.
A user asks a question.
The AI expands that question into multiple related searches, looks for reliable sources, compares information across several pages, and then generates a response.
The process looks something like this:
User Question
↓
Query Expansion
↓
Search Index
↓
Retrieve Trusted Sources
↓
Evaluate Authority
↓
Generate Response
↓
Citations
Two questions determine whether your content has a chance of appearing:
Can the system access your content?
Is the content structured well enough to understand?
My portfolio failed the first question.
Everything else became irrelevant.
The Problems I Found on My Own Website
Instead of theoretical advice, here’s what I actually discovered while auditing my portfolio.
- Blog content wasn’t available without JavaScript The articles only appeared after the application hydrated in the browser.
For human visitors that wasn’t a problem.
For crawlers relying on the initial HTML response, the blog effectively didn’t exist.
- Missing Article Schema Each blog post lacked structured data such as:
Article
Blog Posting
Without these signals, search engines have to infer what the page represents instead of being told directly.
- Missing Person & Organization Schema Although my name appeared throughout the site, there was no structured connection between:
Jaimin Umaraniya
Portfolio
LinkedIn
GitHub
Technical expertise
Those relationships matter when building entity authority.
- Weak Trust Signals Individual articles didn’t include:
Author information
Published date
Last updated date
Small details like these improve both user trust and machine understanding.
- Poor Internal Linking Each article existed on its own.
There were very few connections between blog posts, projects, or case studies.
Write on Medium
A knowledge base should behave like a network, not a collection of isolated pages.
My AI SEO Checklist for 2026
After reviewing my own website, I created a practical checklist that I’m implementing across every page.
Rendering & Crawlability
Server-side rendering (SSR) or Static Site Generation (SSG)
Verify content appears in raw HTML
Submit XML Sitemap
Configure robots.txt correctly
Add canonical URLs
Ensure pages return proper HTTP status codes
Structured Data
Article Schema
Blog Posting Schema
Person Schema
Organization Schema
Breadcrumb Schema
FAQ Schema
Software-Application Schema (for projects)
Content Quality
Every article should include:
A clear answer near the beginning
Real examples
Original screenshots
Code snippets where relevant
Logical heading hierarchy
Practical takeaways
Entity SEO
Maintain consistency across your website and profiles:
Full name
Professional title
Portfolio
LinkedIn
GitHub
Technology stack
Consistency helps search engines understand who you are and what topics you’re associated with.
Internal Linking
Every article should connect to:
Related blog posts
Relevant project case studies
Documentation
Tutorials
Resource pages
Good internal linking helps both readers and crawlers navigate your content.
Image Optimization
Every image should have:
Descriptive filenames
Meaningful alt text
Responsive formats
Proper compression
Open Graph compatibility
What Agentic Browsers Look For
AI-powered browsers and autonomous agents don’t simply index pages.
They evaluate them.
When visiting a website, they often look for answers to questions like:
Can this page answer the user’s question immediately?
Is the information current?
Is the author clearly identified?
Are claims supported by evidence?
Can I navigate to related information?
If your website behaves like a well-organized knowledge base, AI systems can understand it much more effectively.
Three AI SEO Myths Worth Ignoring
Myth 1: Adding an llms.txt file guarantees AI visibility
It may help certain tools discover your website, but it won’t fix poor content, weak structure, or missing crawlability.
Myth 2: Publishing hundreds of AI-generated articles builds authority
Quantity rarely beats originality.
A handful of well-researched articles with practical examples will almost always outperform dozens of generic posts.
Myth 3: Keyword density is still the most important ranking factor
Modern search focuses much more on understanding, context, and quality than simple keyword repetition.
Write naturally.
Structure your content well.
Solve real problems.
My 90-Day Improvement Plan
Here’s the roadmap I’m following for my own portfolio.
Weeks 1–2
Move blog pages to SSR or SSG
Verify content appears in raw HTML
Weeks 3–4
Add structured data
Generate a dynamic sitemap
Improve metadata
Weeks 5–6
Add author profiles
Improve internal linking
Add publication dates
Weeks 7–8
Rewrite older articles with better examples
Add diagrams and code samples
Weeks 9–12
Monitor Google Search Console
Track indexing improvements
Continue publishing high-quality technical content
Final Thoughts
Building an AI-ready website isn’t about chasing another ranking factor.
It’s about creating a website that’s easy to understand — for both people and machines.
If your content can’t be accessed, structured, and trusted, it becomes much harder for search engines and AI systems to surface it, regardless of how well it’s written.
Traditional SEO is still the foundation.
The difference today is that your website also needs to be readable, connected, and structured for the next generation of search.
About the Author
I’m Jaimin Umaraniya, a Full-Stack Developer focused on building modern web applications with React, Next.js, AI-powered SaaS, Technical SEO, and performance-first architecture.
Through my technical articles and real-world case studies, I share practical insights on software engineering, frontend architecture, modern SEO, and building products that are both user-friendly and search-friendly.
If you’d like to explore more of my work, visit my portfolio:
🌐 Portfolio: https://portfoliojaimin.netlify.app
💼 LinkedIn: https://linkedin.com/in/jaimin2106
If you’ve audited your own website and discovered similar issues — or found something completely different — I’d genuinely enjoy hearing about your experience. Technical discussions like these help all of us build better products.
Top comments (0)