Q248: SEO, Metadata, Structured Data and Performance

What Interviewers Want To Evaluate

Interviewers want to know whether you can make content discoverable without hurting performance or correctness.

They check metadata, canonical URLs, robots behavior, sitemap, structured data, social previews, Core Web Vitals, server rendering, duplicate content, and how SEO requirements affect frontend architecture.

Short Interview Answer

SEO for a content-heavy frontend depends on crawlable HTML, accurate metadata, canonical URLs, sitemap coverage, structured data where useful, and good Core Web Vitals. I keep important content server-rendered or statically generated, avoid hiding primary content behind client-only JavaScript, generate route-specific titles and descriptions, and ensure metadata stays aligned with localized and canonical content.

Detailed Interview Answer

SEO is not only keywords.

Technical SEO includes:

crawlable content
metadata
canonical URLs
sitemaps
robots rules
structured data
social previews
performance
mobile usability
duplicate content control

Frontend architecture affects all of these.

Crawlable Content

Search engines need content they can discover.

For handbook pages:

question title
answer sections
code examples
topic structure
internal links

Server-rendered or statically generated content is usually safer for important public pages.

Do not require client JavaScript to reveal primary content.

Metadata

Each page should have specific metadata.

title
description
canonical URL
open graph title
open graph description
image when useful

Generic metadata weakens search and sharing previews.

Canonical URLs

Canonical URLs tell search engines the preferred URL.

Use them when content may be reachable through multiple paths.

Examples:

/questions/q001
/topics/javascript?q=q001
tracking parameters
localized alternatives

Canonical strategy prevents duplicate-content confusion.

Sitemap

Sitemaps help discovery.

Include:

question pages
topic pages
volume pages
docs pages
important static pages

Keep it updated as content grows.

For large content systems, generate it from source metadata.

Structured Data

Structured data helps machines understand content.

Possible types:

Article
FAQPage when truly FAQ-like
BreadcrumbList
Course or LearningResource where appropriate

Use structured data honestly.

Do not mark content as FAQ if it is not formatted and visible as FAQ.

Performance And SEO

Core Web Vitals influence user experience and can affect search performance.

Important:

LCP for main content
INP for interactive pages
CLS for stable layout
mobile performance
image optimization
font strategy

SEO and performance are aligned for content pages.

Internal Linking

Internal links help users and crawlers.

Good structures:

previous and next question links
topic pages
volume pages
batch pages
related content
breadcrumbs

Avoid orphan pages.

As the handbook grows, navigation becomes SEO infrastructure.

Robots Rules

Robots rules should be intentional.

Allow:

public handbook content
topic pages
documentation pages

Block or noindex:

private pages
duplicate utility routes
internal search results if low value
temporary previews

Do not accidentally noindex important pages.

Common Mistakes

Common mistakes include:

same title on every page
missing canonical URLs
primary content hidden behind client rendering
stale sitemap
incorrect structured data
slow mobile pages
orphan content
localized metadata missing

SEO bugs are often content architecture bugs.

Senior Trade-Offs

Trade-offs:

static generation vs build time
rich structured data vs maintenance
client personalization vs crawlability
canonical simplicity vs flexible routing
large sitemap vs generation complexity

Choose based on content value and scale.

Interview Framing

In an interview, say:

I make important content crawlable, generate route-specific metadata and canonical URLs, keep sitemap and internal links updated, use structured data honestly, and protect Core Web Vitals for public pages.

Revision Notes

• SEO needs crawlable content and accurate metadata.
• Canonical URLs prevent duplicate confusion.
• Sitemaps should be generated from content metadata.
• Structured data must match visible content.
• Core Web Vitals matter for public content UX.
• Internal links help both users and crawlers.

Follow-Up Questions

• Why is client-only content risky for SEO?
• What does a canonical URL solve?
• What should a sitemap include?
• When should structured data be used?
• How do Core Web Vitals affect SEO strategy?

How I Would Answer This In A Real Interview

I would say technical SEO starts with making the actual content available in HTML, then adding accurate metadata, canonical URLs, sitemap entries, internal links, and structured data where appropriate. I would keep public handbook pages statically generated or server-rendered, avoid client-only primary content, and measure mobile Core Web Vitals because discoverability and user experience reinforce each other.