DEV Community: Mritunjoy Mondal

How to Make Your Site Show in ChatGPT Answers (A Developer's Guide)

Mritunjoy Mondal — Sat, 24 Oct 2026 18:30:00 +0000

ChatGPT now answers millions of questions with live web results and source links. If your site isn't one of those sources, you're invisible to a growing chunk of searchers.

To show up in ChatGPT answers, you need four things: let OpenAI's crawlers in, be indexed in the search engines ChatGPT relies on, serve content that works without JavaScript, and write answers clear enough to quote. Here's how to do each one, with code.

How ChatGPT Finds Websites

ChatGPT uses two kinds of knowledge:

Source	What it is	Can you influence it?
Training data	What the model learned before its cutoff	Slowly, over time
Live search	Real-time web results with citations	Yes, today

Live search is where you win. When a user asks something current or specific, ChatGPT searches the web, reads pages, and cites the ones it uses. It relies on its own crawler plus third-party search providers, so being well indexed in Bing as well as Google matters.

Step 1: Allow OpenAI's Crawlers

OpenAI uses separate user agents for different jobs:

User agent	Purpose
`OAI-SearchBot`	Finds pages for ChatGPT search results
`ChatGPT-User`	Fetches a page when a user asks ChatGPT to visit it
`GPTBot`	Collects data for model training

If you only want citations, not training, allow search and block training:

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: GPTBot
Disallow: /

Sitemap: https://example.com/sitemap.xml

Want maximum visibility? Allow GPTBot too. Being in training data helps the model know your brand even without search.

Check your CDN and firewall

This is the silent killer. Many sites allow bots in robots.txt but block them at the network level.

Cloudflare: check Security > Bots and the AI crawler settings. Cloudflare can block AI bots by default on some plans
WAF rules: look for rules blocking unknown user agents
Rate limits: aggressive limits can cut crawlers off mid-crawl

Test with curl:

curl -A "OAI-SearchBot/1.0" -I https://example.com/

You want 200 OK, not 403 or a challenge page.

Step 2: Get Indexed in Bing

Since ChatGPT search draws on third-party providers, Bing indexing is worth the 10 minutes.

Sign up for Bing Webmaster Tools
Import your site from Google Search Console (one click)
Submit your sitemap
Turn on IndexNow so new pages get picked up fast

IndexNow ping example:

curl "https://api.indexnow.org/indexnow?url=https://example.com/new-post&key=YOUR_KEY"

Most SEO plugins (Rank Math, Yoast) support IndexNow natively.

Step 3: Serve Content Without JavaScript

Most AI crawlers fetch raw HTML and do not run JavaScript. If your content loads client side, they see an empty <div id="root"></div>.

See what crawlers see:

curl -s https://example.com/blog/post | grep -i "<h1"

No H1 in the output? Your content is invisible to AI.

Fix:

Use SSR or static generation (Next.js, Nuxt, Astro, SvelteKit, Remix)
At minimum, server render the title, headings, main text, and links
Don't hide key answers behind tabs or "load more" buttons that need JS

// Next.js App Router: server component by default, rendered as HTML
export default async function Page() {
  const post = await getPost();
  return (
    <article>
      <h1>{post.title}</h1>
      <div dangerouslySetInnerHTML={{ __html: post.html }} />
    </article>
  );
}

Step 4: Write Answers AI Can Quote

AI tools pull short, clear passages. Structure your content so any section can stand alone.

Answer-first pattern:

## What is schema markup?

Schema markup is structured data that tells search engines what
your page is about. It uses the schema.org vocabulary, usually
added as a JSON-LD script.

Rules that work:

Use the question as the heading
Answer in the first 1 to 2 sentences under it
Then add detail, examples, and steps
Use tables for comparisons and numbered lists for steps
Include specific facts, numbers, and dates
Keep one idea per section

Bad: "In today's fast-paced digital landscape, many factors come into play..."

Good: "Use JSON-LD. Google recommends it because it sits in one script block and doesn't touch your HTML."

Step 5: Make Your Brand a Clear Entity

AI needs to know who you are before it trusts you as a source. Add Organization and Person schema:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Co",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://github.com/example",
    "https://dev.to/example"
  ]
}

Also:

Use the same brand name, description, and bio everywhere
Add an About page with real credentials
Put author names and bios on every article

Step 6: Get Mentioned on Other Sites

AI tools trust what many sources agree on. A brand mentioned across trusted sites gets cited more.

Publish on platforms like DEV, Hashnode, and Medium
Answer questions on Reddit and Stack Overflow (genuinely, not spam)
Get listed in real industry directories
Earn mentions in roundups and comparison articles

Mentions matter here even without a link.

What About llms.txt?

llms.txt is a proposed file at /llms.txt that gives AI tools a clean markdown map of your site.

# Example Co

> Example Co builds developer tools for API testing.

## Docs
- [Getting Started](https://example.com/docs/start): Install and first request
- [API Reference](https://example.com/docs/api): All endpoints

Honest take: it's cheap to add, but there's no confirmation that major AI search tools use it for citations yet. Add it if you like, but do Steps 1 to 6 first.

How to Track ChatGPT Traffic

ChatGPT usually adds utm_source=chatgpt.com to links it cites.

In GA4: Reports > Acquisition > Traffic acquisition > filter source for chatgpt.com

In server logs:

grep -E "OAI-SearchBot|ChatGPT-User|GPTBot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head

This shows which pages OpenAI's bots visit most.

Manual check: ask ChatGPT questions your page answers and see if you're cited. Do it monthly.

Quick Checklist

[ ] OAI-SearchBot and ChatGPT-User allowed in robots.txt
[ ] CDN and firewall not blocking AI bots
[ ] Site verified in Bing Webmaster Tools
[ ] IndexNow turned on
[ ] Main content visible in raw HTML (curl test)
[ ] Question headings with direct answers
[ ] Organization and author schema added
[ ] Brand mentioned on other trusted sites
[ ] Tracking ChatGPT referrals in GA4

Wrapping Up

Showing up in ChatGPT isn't magic. It's crawlability, indexing, clean HTML, and content that answers questions directly. Most of it is the same work as good SEO, with a few extra technical checks.

I write more about this kind of AI search optimization, also called GEO, on my blog. Has ChatGPT cited your site yet? Share how in the comments.

I'm Mritunjoy Mondal, an AI, GEO and Local SEO expert from India.

Schema Markup Guide for Developers: JSON-LD Examples You Can Copy

Mritunjoy Mondal — Tue, 20 Oct 2026 13:02:00 +0000

Schema markup is structured data that tells search engines exactly what your page is about: an article, a product, a business, a person. Add it with a small JSON-LD script, and Google can show rich results like stars, prices, and breadcrumbs. AI tools like ChatGPT and Google AI Overviews also use it to understand who you are.

This guide gives you copy-paste JSON-LD for the schema types that actually matter, plus how to add it in plain HTML, Next.js, and WordPress.

What Is Schema Markup?

Schema markup is a shared vocabulary from schema.org that labels your content in a machine-readable way.

Without schema, Google reads "4.8" on your page and has to guess. With schema, you tell it: this is an aggregateRating with a ratingValue of 4.8 from 120 reviews.

JSON-LD vs Microdata vs RDFa

Format	How it works	Use it?
JSON-LD	Separate `<script>` block	Yes. Google recommends it
Microdata	Attributes inside HTML tags	Only for legacy sites
RDFa	Attributes inside HTML tags	Rarely

JSON-LD wins because it lives in one block, doesn't touch your markup, and is easy to generate from data.

The Basic Structure

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup Guide for Developers"
}
</script>

@context is always https://schema.org
@type is the thing you are describing
Everything else is properties of that type

You can place it in <head> or <body>. Both work.

1. Organization Schema (Every Site)

Put this on your homepage. It defines your brand as an entity.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Co",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://x.com/example",
    "https://github.com/example"
  ]
}

sameAs connects your site to your social profiles. This helps Google and AI tools confirm your brand is one consistent entity.

2. Article Schema (Blog Posts)

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema Markup Guide for Developers",
  "image": "https://example.com/images/schema-guide.jpg",
  "datePublished": "2026-10-16",
  "dateModified": "2026-10-16",
  "author": {
    "@type": "Person",
    "name": "Jane Dev",
    "url": "https://example.com/about/"
  },
  "publisher": { "@id": "https://example.com/#organization" }
}

Keep dateModified honest. Only update it when the content really changes.

3. BreadcrumbList Schema

Shows a clean path in search results instead of a raw URL.

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog/" },
    { "@type": "ListItem", "position": 3, "name": "Schema Guide" }
  ]
}

The last item can skip item since it is the current page.

4. Product Schema (E-commerce)

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wireless Mechanical Keyboard",
  "image": "https://example.com/keyboard.jpg",
  "sku": "KB-2026",
  "brand": { "@type": "Brand", "name": "KeyCo" },
  "offers": {
    "@type": "Offer",
    "price": "79.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/keyboard"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "214"
  }
}

Price and rating must match what users see on the page. Mismatches can cost you rich results.

5. LocalBusiness Schema (Local SEO)

For any business with a physical location or service area.

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "City Plumbing Co",
  "url": "https://cityplumbing.com/",
  "telephone": "+1-555-123-4567",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78701",
    "addressCountry": "US"
  },
  "openingHours": "Mo-Fr 08:00-18:00",
  "areaServed": ["Austin", "Round Rock", "Cedar Park"]
}

Use the most specific type you can (Plumber, Dentist, Restaurant) instead of plain LocalBusiness. Name, address, and phone must match your Google Business Profile exactly.

6. FAQPage Schema

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Does schema markup improve rankings?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Not directly. It helps search engines understand your page and can unlock rich results that improve click-through rate."
      }
    }
  ]
}

Reality check: Google now shows FAQ rich results mainly for well-known government and health sites. It is still worth adding because other search engines and AI tools can read it, but don't expect FAQ dropdowns in Google for most sites.

Linking Schema Together with @graph

Instead of separate blocks, connect everything in one graph using @id.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Co",
      "url": "https://example.com/"
    },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "https://example.com/",
      "publisher": { "@id": "https://example.com/#organization" }
    },
    {
      "@type": "Article",
      "headline": "Schema Markup Guide for Developers",
      "isPartOf": { "@id": "https://example.com/#website" },
      "publisher": { "@id": "https://example.com/#organization" }
    }
  ]
}

This tells search engines these are related entities, not random separate facts.

How to Add Schema in Next.js (App Router)

export default function BlogPost({ post }) {
  const jsonLd = {
    '@context': 'https://schema.org',
    '@type': 'Article',
    headline: post.title,
    datePublished: post.publishedAt,
    author: { '@type': 'Person', name: post.author },
  };

  return (
    <>
      <script
        type="application/ld+json"
        dangerouslySetInnerHTML={{
          __html: JSON.stringify(jsonLd).replace(/</g, '\\u003c'),
        }}
      />
      <article>{/* content */}</article>
    </>
  );
}

The .replace(/</g, '\\u003c') escapes < so user content can't break out of the script tag.

How to Add Schema in WordPress

Install Rank Math or Yoast. Both add Organization, Article, and Breadcrumb schema automatically
For custom types, use the plugin's schema builder
Avoid stacking two SEO plugins. You'll get duplicate schema

How to Test Your Schema

Google Rich Results Test: shows which rich results your page qualifies for
Schema Markup Validator (validator.schema.org): checks any schema.org type, not just Google ones
Search Console > Enhancements: shows errors across your whole site after Google crawls it

Test before every deploy that touches templates.

Common Schema Mistakes

Marking up content that isn't visible on the page
Fake reviews or ratings in schema (can lead to a manual action)
Prices in schema that don't match the page
Duplicate schema from multiple plugins
Using LocalBusiness with an address you don't actually have
Forgetting to update schema when page content changes

Does Schema Help Rankings?

Not directly. Schema is not a ranking factor by itself. What it does:

Unlocks rich results, which can raise click-through rate
Helps Google understand entities and relationships
Makes your content easier for AI search tools to parse and cite

Think of it as making your site easier to read for machines, not as a ranking trick.

Quick Starter Checklist

[ ] Organization + WebSite schema on homepage
[ ] Article schema on blog posts
[ ] BreadcrumbList on all inner pages
[ ] Product schema on product pages
[ ] LocalBusiness schema for local businesses
[ ] Tested in Rich Results Test
[ ] No errors in Search Console

Wrapping Up

Start with Organization, Article, and Breadcrumb schema. That covers most sites. Add Product or LocalBusiness if they fit your business, test everything, and keep it in sync with the visible page.

If you want to see how schema fits into a full technical SEO setup, I share more guides on my SEO blog. Got a schema error you can't fix? Drop it in the comments.

I'm Mritunjoy Mondal, an AI, GEO and Local SEO expert from India.

7 SEO Mistakes Developers Make (and How to Fix Them in Code)

Mritunjoy Mondal — Fri, 16 Oct 2026 17:50:17 +0000

You built a fast, clean site. It still doesn't rank. In most audits I run, the problem isn't content. It's small dev decisions that quietly block Google.

Here are the 7 mistakes I see most, with the code to fix each one.

1. Blocking Google in robots.txt

A staging rule gets pushed to production and the whole site disappears from Google.

Bad:

User-agent: *
Disallow: /

Fix:

User-agent: *
Disallow: /admin/
Sitemap: https://yoursite.com/sitemap.xml

Always check yoursite.com/robots.txt after every deploy.

2. Leaving noindex on live pages

Same story, different file. A noindex meta tag from staging survives launch.

<!-- Remove this on production -->
<meta name="robots" content="noindex, nofollow">

Pro tip: control it with an env variable so it can never leak.

const robots = process.env.NODE_ENV === 'production'
  ? 'index, follow'
  : 'noindex, nofollow';

3. Content that only exists after JavaScript runs

If your page is empty until React fetches data, Google may index a blank page or delay indexing for weeks.

Fix:

Use SSR or SSG (Next.js, Nuxt, Astro, SvelteKit)
At least render title, H1, main text and links on the server
Test with Search Console > URL Inspection > View crawled page

4. Missing or duplicate titles

Every page shipping with the same <title>My App</title> is one of the most common issues I find.

Next.js example:

export const metadata = {
  title: 'Local SEO Checklist for Small Businesses',
  description: 'A step by step local SEO checklist to rank in Google Maps.',
  alternates: { canonical: 'https://yoursite.com/local-seo-checklist' },
};

Rules:

Unique title per page, under 60 characters
Unique description, around 150 characters
Self-referencing canonical on every page

5. Using divs and buttons instead of real links

Google follows <a href>. It does not click your buttons.

Bad:

<div onclick="router.push('/pricing')">Pricing</div>

Good:

<a href="/pricing">Pricing</a>

If Google can't follow your navigation, it can't find your pages.

6. Ignoring Core Web Vitals

Speed is a ranking signal and a conversion killer.

Metric	Target	Common dev fix
LCP	Under 2.5s	Preload hero image, serve WebP/AVIF
INP	Under 200ms	Split bundles, defer third party scripts
CLS	Under 0.1	Set width and height on images and embeds

<link rel="preload" as="image" href="/hero.webp">
<img src="/hero.webp" width="1200" height="600" alt="Product dashboard">

7. No structured data

Schema helps Google and AI tools like ChatGPT understand who you are and what the page is about.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "7 SEO Mistakes Developers Make",
  "author": {
    "@type": "Person",
    "name": "Mritunjoy Mondal",
    "url": "https://mritunjoymondal.com/"
  }
}
</script>

Validate it with Google's Rich Results Test before you ship.

Pre-launch SEO checklist

Copy this into your PR template:

[ ] robots.txt allows crawling
[ ] No noindex on production
[ ] Main content renders server side
[ ] Unique title, description, canonical per page
[ ] Navigation uses real <a href> links
[ ] Images have width, height, alt text
[ ] XML sitemap live and submitted
[ ] Schema validated

Wrapping up

None of these are hard fixes. They're just easy to miss when you're shipping fast. Fix them once, add them to your checklist, and your next launch starts with a clean SEO foundation.

I write more practical guides like this on technical SEO and AI search. If your site is live but not ranking, drop a comment and I'll point out what to check first.

I'm Mritunjoy Mondal, an AI, GEO and Local SEO expert from India.