Top 30 Content & Copywriting Interview Questions and Answers

30 questions. Pick an answer, or open “Show the answer” to read it.

Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.

1. Question 1 of 30

   Why should a migration CLI README place a comparison table against alternatives before the detailed configuration reference?

   • aDevelopers evaluating tools need to justify switching costs before they will invest time learning configuration details
   • bTechnical readers prefer to scan alternatives after they have fully mastered the tool's settings
   • cConfiguration options change frequently, so placing them later reduces maintenance burden
   • dComparison tables improve GitHub SEO ranking when placed in the first half of the document
   Show the answer

   Answer: a · Developers evaluating tools need to justify switching costs before they will invest time learning configuration details

   Developers must understand competitive differentiation and justify switching before investing in configuration details, matching the attention-to-trust adoption funnel. Option C raises a valid docs concern but misattributes the ordering rationale, since the sequence serves persuasion rather than maintenance ease.

   Read the full bite: Outline README sections for a migration CLI and explain persuasion

2. Question 2 of 30

   Which approach best demonstrates progressive disclosure applied specifically to UI copy and tooltips?

   • aReserve progressive disclosure for navigation menus while keeping all setting descriptions equally detailed
   • bDisplay all help text inline to minimize clicks and maximize discoverability
   • cReplace tooltips with a single help link to reduce on-screen text
   • dUse short tooltips for common cases and hide advanced details behind clearly labeled expanders or secondary sheets
   Show the answer

   Answer: d · Use short tooltips for common cases and hide advanced details behind clearly labeled expanders or secondary sheets

   Option D correctly applies progressive disclosure by splitting primary tooltips from secondary details, which reduces cognitive load and error rates for novices while keeping experts efficient. Option B is tempting but wrong because dumping all help text inline eliminates clicks at the cost of overwhelming novices with irrelevant details.

   Read the full bite: How would you apply progressive disclosure to UI copy and tooltips?

3. Question 3 of 30

   Which documentation strategy best protects both users and the business for an API endpoint that triggers irreversible data loss?

   • aInclude a concise 'be careful' note inline within the parameter table to avoid disrupting the page flow.
   • bUse a distinct WARNING admonition that names the hazard, states the consequence, and gives an escape route using direct imperatives.
   • cPlace a CAUTION call-out in a distinct block advising developers to back up data when possible.
   • dPrefix the endpoint with DANGER and enumerate every possible risk to ensure comprehensive legal coverage.
   Show the answer

   Answer: b · Use a distinct WARNING admonition that names the hazard, states the consequence, and gives an escape route using direct imperatives.

   A distinct WARNING admonition following the SAFE method—Signal, Hazard, Consequence, Escape—applies the correct severity level for irreversible data loss and uses direct imperatives that are legally defensible and actionable. Option D is tempting but wrong because DANGER is reserved for life-threatening scenarios, and over-warning desensitizes developers while diluting the impact of truly critical alerts.

   Read the full bite: How would you document a destructive API endpoint safely?

4. Question 4 of 30

   Which conventional commit best documents a fix for a date sorter that incorrectly assumed US locale formats?

   • afix: resolve date sorting bug
   • bfix(date-parser): date sorting was fixed for non-US formats with no additional body
   • cfix(date-parser): handle locale-aware date sorting with body noting the previous hardcoded US locale assumption
   • dfeat(date-parser): add locale-aware date sorting with body describing browser locale detection
   Show the answer

   Answer: c · fix(date-parser): handle locale-aware date sorting with body noting the previous hardcoded US locale assumption

   Option C correctly uses the fix type and date-parser scope, an imperative subject, and a body that explains the root cause to prevent future regressions. Option D is a tempting distractor because the change does add locale logic, but feat signals a minor SemVer bump and misrepresents a bug patch.

   Read the full bite: Write a conventional commit for a non-US date sorting bug

5. Question 5 of 30

   What single element most reduces churn when documenting a breaking API change for developers?

   • aA celebratory tone emphasizing new features
   • bA longer, fully chronological changelog of every commit
   • cRemoving mention of the old behavior entirely
   • dConcrete before-and-after migration steps for each breaking change
   Show the answer

   Answer: d · Concrete before-and-after migration steps for each breaking change

   Developers churn when they cannot see how to fix their code; explicit before-and-after migration steps give a direct, actionable path. A celebratory tone or hiding the old behavior leaves users stranded and increases frustration.

   Read the full bite: Structuring release notes for breaking API changes

6. Question 6 of 30

   When A/B testing sign-up button copy, which practice ensures you can accurately attribute differences in sign-ups to the copy change?

   • aRandomly assign users to variants using a hashed user ID, track impressions and conversions, and compare conversion rates
   • bShow version A for one week and version B for the next to avoid overlap
   • cSplit users by geolocation and compare sign-up counts across regions after two weeks
   • dTrack button clicks for each variant and compare click counts, assuming more clicks lead to more sign-ups
   Show the answer

   Answer: a · Randomly assign users to variants using a hashed user ID, track impressions and conversions, and compare conversion rates

   Randomizing with hashed user IDs and tracking both impressions and completed sign-ups lets you calculate a true conversion rate and establish causality. Sequential testing introduces temporal bias because traffic composition and external factors differ between weeks, invalidating the comparison.

   Read the full bite: How would you A/B test sign-up button copy and measure results?

7. Question 7 of 30

   Which approach best implements click tracking for dozens of headlines and CTAs while remaining performant and maintainable?

   • aAttach a unique addEventListener to each element and use its innerText as the analytics identifier
   • bUse a single delegated listener on a parent container, read data attributes to identify elements, and send via navigator.sendBeacon
   • cRe-attach individual listeners to all elements whenever new content is injected into the page
   • dAdd inline onclick handlers to every element that submit CSS class names to the analytics endpoint
   Show the answer

   Answer: b · Use a single delegated listener on a parent container, read data attributes to identify elements, and send via navigator.sendBeacon

   Event delegation on a common ancestor avoids the performance cost of dozens of individual listeners and naturally handles dynamic content, while data attributes provide stable identifiers unlike brittle innerText or class names. The most tempting distractor, attaching unique listeners to every element, scales poorly and misses the efficiency and dynamic-content benefits that delegation provides.

   Read the full bite: How would you track clicks on headlines and calls-to-action?

8. Question 8 of 30

   When merging anonymous analytics events with CRM data to auto-segment users by persona, what identity handling step best distinguishes a robust architecture from a fragile one?

   • aBuild a golden record from CRM data first, then apply ML clustering on behavioral signals separately before attempting any cross-source joins
   • bDirectly join the analytics and CRM tables on email address and discard all anonymous events to prevent null matches
   • cLoad CRM snapshots as the primary table and append only post-authentication clickstream events that contain a matching email to reduce latency
   • dIngest both sources into common storage, then stitch anonymous IDs to CRM identifiers using deterministic or probabilistic matching while maintaining confidence scores
   Show the answer

   Answer: d · Ingest both sources into common storage, then stitch anonymous IDs to CRM identifiers using deterministic or probabilistic matching while maintaining confidence scores

   The correct answer treats identity resolution as a first-class problem by linking anonymous and known IDs with confidence scoring, preserving pre-authentication behavior. Option B is the most tempting distractor because joining on email seems straightforward but ignores anonymous users, data quality issues like typos, and merge conflicts.

   Read the full bite: How to merge analytics and CRM data to auto-segment users by persona

9. Question 9 of 30

   Which evaluation sequence best balances accuracy, latency, and robustness when personalizing a homepage hero by industry in real time?

   • aRequire user login before showing any hero, use IP lookup only to validate profile data, and block rendering until the segment is confirmed.
   • bCheck the user profile industry first, then enrich unknown users via IP or domain, then infer from behavior, and serve a default hero if signals are absent or time out.
   • cRun a deep-learning classifier on behavioral data first, then check the user profile, then query third-party IP enrichment, with no fallback if all signals fail.
   • dPrompt every visitor with an industry survey modal, cache the response for one day, and skip third-party enrichment to avoid privacy compliance.
   Show the answer

   Answer: b · Check the user profile industry first, then enrich unknown users via IP or domain, then infer from behavior, and serve a default hero if signals are absent or time out.

   Option B follows the highest-confidence-first hierarchy (explicit short-circuits implicit, which short-circuits inference) and includes a critical fallback for latency or missing data. Option C exemplifies the common anti-pattern of over-engineering with deep learning and failing to define a default state.

   Read the full bite: Design backend logic for personalized hero by industry

10. Question 10 of 30

    Which architectural approach best demonstrates a production-ready, polite, and legally defensible competitor sitemap scraper for extracting H1 tags and word counts?

    • aUse an async client with retry logic, parse HTML with regex to minimize dependencies, enforce rate limits only after receiving HTTP 429 errors, and defer legal review until the dataset is complete.
    • bUse an async client with capped concurrency and exponential backoff, handle sitemap index files with namespace-aware XML parsing, extract H1 and word count with a lenient DOM parser, enforce rate limits, honor robots.txt, and seek legal review before commercial use.
    • cUse an async client with unlimited workers for speed, parse flat sitemap files while ignoring sitemap indexes, skip deduplication to reduce complexity, and treat a public sitemap as implicit commercial-use license.
    • dUse an async client with retry logic, parse sitemaps with a standard XML parser that ignores namespaces, extract H1 with a DOM parser, and omit proactive rate limiting in favor of dynamic backoff only when receiving 429 responses.
    Show the answer

    Answer: b · Use an async client with capped concurrency and exponential backoff, handle sitemap index files with namespace-aware XML parsing, extract H1 and word count with a lenient DOM parser, enforce rate limits, honor robots.txt, and seek legal review before commercial use.

    Option B is correct because it combines throttled async fetches, proper sitemap and HTML parsing, proactive rate limiting, robots.txt compliance, and legal review. Option D is tempting because it includes async retries and DOM parsing, but it fails to handle XML namespaces or proactively rate-limit, which risks breaking on sitemap indexes and overwhelming the target server.

    Read the full bite: Build a competitor sitemap scraper for H1 and word count

11. Question 11 of 30

    When designing a pipeline to discover unknown pain-point categories from thousands of unstructured reviews, which sequence best ensures valid grouping and reliable severity ranking?

    • aFeed raw reviews directly into an LLM for summarization, then rank the most frequent terms as the top pain points.
    • bTokenize and remove stopwords, then run sentiment analysis on the full corpus before grouping reviews into predefined product areas.
    • cDeduplicate and normalize the corpus, cluster to discover themes, then apply sentiment analysis within each cluster to rank by severity.
    • dApply supervised classification with a predefined taxonomy, then count negative keywords per class to rank issues.
    Show the answer

    Answer: c · Deduplicate and normalize the corpus, cluster to discover themes, then apply sentiment analysis within each cluster to rank by severity.

    The correct sequence matches the card's recommended lifecycle: preprocess to remove noise and duplicates, use unsupervised clustering to discover emergent themes since categories are unknown, and score sentiment within each cluster to rank pain points by frequency and severity. Option A is a tempting distractor because LLMs are popular, but the card flags jumping straight to summarization without cleaning as a red flag that yields unreliable, unvalidated output.

    Read the full bite: Outline an NLP pipeline to categorize reviews and identify pain points

12. Question 12 of 30

    Why is pure collaborative filtering a poor choice for a brand-new user on a news site?

    • aIt has no interaction history for that user to find similar users
    • bIt cannot represent article text at all
    • cIt is always slower than content-based filtering
    • dIt ignores how recently an article was published
    Show the answer

    Answer: a · It has no interaction history for that user to find similar users

    Collaborative filtering needs a user's behavior to match them to similar users, which a brand-new user lacks, causing the cold-start problem. Content-based methods sidestep this by using article features and the user's very first reads.

    Read the full bite: Design a next-best-article recommender

13. Question 13 of 30

    In a production Thompson Sampling bandit serving headlines with delayed click feedback, which design best balances real-time serving with robust learning?

    • aAllocate traffic randomly for a fixed burn-in period before committing fully to the highest posterior mean
    • bMaintain a minimum traffic percentage per headline and process attributed clicks through an async update pipeline
    • cReserve a small random holdout bucket and feed its outcomes directly into the main bandit's posterior updates
    • dRun nightly batch updates to recalculate Beta posteriors after all clicks are attributed
    Show the answer

    Answer: b · Maintain a minimum traffic percentage per headline and process attributed clicks through an async update pipeline

    Option B correctly combines an exploration floor, which prevents new headlines from being starved before proving themselves, with an async pipeline that handles delayed, out-of-order feedback. Option D represents the common mistake of ignoring real-time constraints with batch updates, while Option A risks premature convergence through greedy allocation.

    Read the full bite: Propose a multi-armed bandit system to optimize headlines faster

14. Question 14 of 30

    When building a centralized copy service for a React app, which design choice best ensures consistency without over-engineering?

    • aHardcode user-facing strings directly inside JSX components to keep markup simple
    • bStore static copy in a remote database and fetch it on every component mount
    • cUse semantic identifiers like button.save in a key-value map consumed via a hook
    • dUse the exact English display text as the lookup key for easy readability
    Show the answer

    Answer: c · Use semantic identifiers like button.save in a key-value map consumed via a hook

    Semantic identifiers decouple content from components, so rewording copy only requires updating the map. Using exact English text as keys (D) is brittle because changing a label breaks every reference across the codebase.

    Read the full bite: How would you design a centralized copy service for consistent UI text?

15. Question 15 of 30

    When architecting a single application to serve multiple distinct brand voices, which pattern best prevents operational sprawl?

    • aStore brand copy in JSON files within the repository and import them into shared components
    • bExtend a monolithic CMS with tenant-specific page templates that handle both content and rendering
    • cMaintain separate frontend repositories per tenant so each brand can customize layouts independently
    • dUse a headless CMS with tenant-scoped content spaces and resolve brand voice via domain or header
    Show the answer

    Answer: d · Use a headless CMS with tenant-scoped content spaces and resolve brand voice via domain or header

    A headless CMS with tenant isolation allows copy changes without code releases and keeps UI components brand-agnostic. Storing copy in repository JSON files seems like separation but still forces a deployment for every text tweak and lacks cross-tenant governance.

    Read the full bite: How would you architect a white-label content system for multiple brand voices?

16. Question 16 of 30

    You need to add a forbidden-word check to a React app's CI pipeline. Which approach best prevents user-facing policy violations while keeping the signal-to-noise ratio low?

    • aExtract string literals from a framework-specific user-facing hook, check against tiered rules with allowlists, and run as a fast PR annotation job.
    • bAdd a mandatory PR checklist asking developers to confirm no forbidden words were added, bypassing the check for internal identifiers.
    • cGrep all source files for forbidden terms and fail the build on any match, requiring content team approval to override.
    • dScan the repository post-deployment and create tickets for the editorial team to review flagged strings within 48 hours.
    Show the answer

    Answer: a · Extract string literals from a framework-specific user-facing hook, check against tiered rules with allowlists, and run as a fast PR annotation job.

    Option A is correct because it targets only user-facing strings via AST-aware extraction, uses severity tiers and allowlists to control noise, and gates pull requests with fast inline feedback. Option C is a tempting distractor because grepping all source files sounds thorough, but it cannot distinguish UI text from variable names or comments, generating false positives that train teams to ignore the check.

    Read the full bite: How would you automate forbidden-word checks in CI/CD?

17. Question 17 of 30

    Which design best implements a headless CMS strategy for managing reusable brand voice copy across multiple channels?

    • aModel each page as a unique content entry containing hardcoded voice metadata so editors can customize every page independently without restrictions
    • bCreate a structured Copy Fragment content type with required Tone and Context fields, enforce character limits at the CMS level, and allow API queries filtered by these metadata fields
    • cStore all copy as rich HTML blobs in the CMS and have clients download the full content library to filter locally for tone and context
    • dKeep the CMS schema generic with plain text fields only, and let frontend developers enforce tone guidelines and character limits per channel
    Show the answer

    Answer: b · Create a structured Copy Fragment content type with required Tone and Context fields, enforce character limits at the CMS level, and allow API queries filtered by these metadata fields

    The correct approach treats the CMS as strategic infrastructure by enforcing brand rules like tone and character limits at the schema level and exposing metadata via API filters so clients fetch only relevant fragments. Distractor B appeals to separation of concerns but wrongly pushes editorial governance out of the CMS, leading to inconsistent brand voice and duplicated validation logic across channels.

    Read the full bite: Design a headless CMS model for brand voice metadata and API usage

18. Question 18 of 30

    Which layered approach best secures a multi-channel notification templating engine?

    • aRegex-based parsing with final HTML sanitization and raw scripting support for flexibility
    • bFormal AST grammar with context-aware auto-escaping and sandboxed rendering with resource limits
    • cString replacement with input validation and HTML entity encoding for all outputs
    • dGrammar-based parsing with output-side HTML sanitization and trusted internal execution
    Show the answer

    Answer: b · Formal AST grammar with context-aware auto-escaping and sandboxed rendering with resource limits

    Option B is correct because defense-in-depth requires an AST whitelist to prevent injection, context-aware escaping tailored to each output channel, and sandboxed execution with resource limits. Option D is tempting because formal parsing is correct, but output-side HTML sanitization alone fails for SMS or JSON contexts and lacks sandboxing against DoS.

    Read the full bite: Design a secure templating engine for user notifications

19. Question 19 of 30

    Which combination of NLP features and dashboard design best operationalizes a simple and empowering brand voice for executive stakeholders?

    • aGeneric sentiment and toxicity classifiers displayed as confusion matrices and perplexity histograms
    • bManual copy review spreadsheets updated quarterly and shared via email summaries
    • cA bespoke 70B parameter LLM trained from scratch with embedding distance heatmaps by product area
    • dReadability scores and agency verb detection rendered as time-series alignment KPIs with team-level drill-downs
    Show the answer

    Answer: d · Readability scores and agency verb detection rendered as time-series alignment KPIs with team-level drill-downs

    The card states that strong answers translate simplicity into readability metrics and empowerment into agency verb detection, then visualize them as business-friendly time-series KPIs with faceted breakdowns. Option A reflects the common error of using generic sentiment tools and technical model metrics, while Option B represents the non-scalable manual review red flag.

    Read the full bite: Propose an NLP approach to audit brand voice and build a dashboard

20. Question 20 of 30

    Which schema design best preserves first normal form for posts that can have multiple tags?

    • aDuplicate the post row for each tag, storing tag names inline with each copy
    • bCreate a dedicated tags table and a post_tags join table linking post_id to tag_id
    • cStore tags as a comma-separated string in a single column on the posts table
    • dCreate a tags table but reference tag_id with a foreign key directly on the posts table
    Show the answer

    Answer: b · Create a dedicated tags table and a post_tags join table linking post_id to tag_id

    A join table models the many-to-many relationship without duplication or parsing strings, satisfying first normal form. Storing comma-separated tags in a single column violates 1NF and prevents indexed lookups, which is why it is flagged as a common anti-pattern.

    Read the full bite: Design a database schema for a blog with posts, authors, and tags

21. Question 21 of 30

    Why model workflow status as a constrained enum or lookup table rather than a free-text column?

    • aIt removes the need for a foreign key to authors
    • bIt prevents inconsistent values and enables reliable filtering and transitions
    • cEnums are always stored in less disk space than text
    • dFree-text columns cannot be indexed in any database
    Show the answer

    Answer: b · It prevents inconsistent values and enables reliable filtering and transitions

    A constrained status set guarantees consistent values, so filters and workflow transitions are reliable; free text invites typos that fragment queries. Storage size and the authors relationship are unrelated to this modeling choice.

    Read the full bite: Data model for an editorial calendar

22. Question 22 of 30

    In the two-table versioning design, what is the main benefit of storing current_version_id in the articles table?

    • aIt serves as a diff baseline to reconstruct any version from deltas
    • bIt enforces referential integrity between articles and their versions
    • cIt lets the application fetch the latest article state without scanning the full version history
    • dIt records the original author who created the article
    Show the answer

    Answer: c · It lets the application fetch the latest article state without scanning the full version history

    The correct answer is C because the pointer provides immediate access to the current snapshot, avoiding costly history scans. Distractor B is wrong since the design intentionally stores full snapshots rather than relying on diff reconstruction for lookups.

    Read the full bite: Design a content versioning system with history and revert

23. Question 23 of 30

    In a decoupled multi-channel architecture, how should article content be stored and delivered to consumers?

    • aIn the website's database with direct SQL access granted to mobile and email services
    • bAs a single shared HTML blob rendered identically by all channels
    • cAs rich text only, requiring each channel to parse the unstructured content for its own needs
    • dIn structured, channel-agnostic fields exposed via an API with channel-specific rendering layers
    Show the answer

    Answer: d · In structured, channel-agnostic fields exposed via an API with channel-specific rendering layers

    Storing content in structured, channel-agnostic fields and delivering it through an API lets each channel render appropriately, while a shared HTML blob is tempting but wrong because forcing identical presentation breaks mobile layouts and email compatibility.

    Read the full bite: Design architecture for multi-channel article distribution from a single source of truth

24. Question 24 of 30

    Which architecture best serves related articles for both archived content and stories published minutes ago?

    • aPre-compute related lists for popular archived articles and run on-the-fly embedding queries with tag fallbacks for breaking news
    • bUse a single monolithic service that computes similarities on every request
    • cApply a heavy deep learning model trained only on user click history to generate all recommendations
    • dPre-compute all similarities nightly and serve exclusively from cache
    Show the answer

    Answer: a · Pre-compute related lists for popular archived articles and run on-the-fly embedding queries with tag fallbacks for breaking news

    This separates offline batch jobs for scale and latency from online serving for freshness, while tag and embedding fallbacks solve the cold-start problem for new articles. Option D is tempting because pre-computation is a valid best practice, yet serving solely from cache cannot handle breaking news published after the last batch run.

    Read the full bite: How would you technically approach building a related articles feature?

25. Question 25 of 30

    How should a high-scale headless CMS prevent thundering herds on a viral article while ensuring newly published edits appear immediately?

    • aUse request coalescing at the origin and actively purge CDN edge nodes via surrogate-key invalidation events on every publish
    • bRely on a short TTL with database query caching and autoscale the origin cluster during traffic spikes
    • cUse stale-while-revalidate at the CDN and schedule periodic cache-warming jobs every five minutes
    • dEmit invalidation events to the CDN but disable origin caching so all requests hit the database for strong consistency
    Show the answer

    Answer: a · Use request coalescing at the origin and actively purge CDN edge nodes via surrogate-key invalidation events on every publish

    Request coalescing collapses concurrent origin fetches for the same key to prevent thundering herds, while surrogate-key invalidation actively clears edge caches on publish instead of waiting for TTL. Option C is tempting because stale-while-revalidate is a valid resilience tactic, but without explicit invalidation it cannot guarantee that a newly published edit appears immediately.

    Read the full bite: Design a highly scalable headless CMS architecture

26. Question 26 of 30

    In a large-scale real-time recommendation funnel with strict latency requirements, what is the defining responsibility of the ranking stage?

    • aPrecompute personalized rankings in a batch pipeline and cache them for hot users to minimize latency
    • bRetrieve hundreds of candidates from millions of items via approximate nearest neighbor search on two-tower embeddings
    • cScore the retrieved candidates using real-time user features and content features with a lightweight model
    • dEnforce business guardrails such as diversity, freshness, and exploration versus exploitation before serving
    Show the answer

    Answer: c · Score the retrieved candidates using real-time user features and content features with a lightweight model

    The ranking stage specifically refers to the lightweight model that scores retrieved candidates using real-time user features and content features. Option D describes re-ranking, which occurs after scoring and applies business guardrails, whereas option B describes candidate generation and option A describes a caching strategy rather than the ranking stage itself.

    Read the full bite: Architect a large-scale real-time recommendation system with data pipelines

27. Question 27 of 30

    When designing automated annual content review for millions of articles, which approach best handles scale, failures, and analytics integration?

    • aA single cron job polling the entire articles table every minute and calling the analytics API inline during flagging
    • bA nightly worker that queries all articles older than one year in one batch and synchronously updates decay scores from the analytics API
    • cA purely event-driven system relying solely on delayed messages without any periodic reconciliation loop
    • dA scheduled workflow using time-range shards and a task queue, with analytics fed by a separate batch pipeline and idempotent workers
    Show the answer

    Answer: d · A scheduled workflow using time-range shards and a task queue, with analytics fed by a separate batch pipeline and idempotent workers

    Time-range shards prevent database overload, a separate batch pipeline decouples analytics rate limits, and idempotent workers handle inevitable retries safely. A purely event-driven system without reconciliation is tempting but dangerous because missed events would leave stale content unreviewed forever.

    Read the full bite: Design a system to automate the content lifecycle

28. Question 28 of 30

    In a rule-based intent classifier, why is the query 'buy discount laptop' labeled transactional?

    • aIt concerns a product category commonly sold online
    • bThe SERP for this query is dominated by e-commerce websites
    • cIt contains action-oriented modifiers indicating the user wants to purchase
    • dIt does not include informational question words like 'how' or 'why'
    Show the answer

    Answer: c · It contains action-oriented modifiers indicating the user wants to purchase

    Transactional intent is defined by the user's goal to complete an action, and rule-based classifiers detect this through modifiers such as 'buy' and 'discount'. Option A is wrong because defining intent by query topic rather than user goal is a common mistake; a laptop query could also be informational.

    Read the full bite: Differentiate informational, navigational, and transactional intent and classify keywords programmatically

29. Question 29 of 30

    When building a content audit tool to evaluate how search engines interpret pages, which three HTML elements should be extracted first?

    • aH1, meta description, and Open Graph tags
    • bTitle tag, H1, and meta description
    • cTitle tag, H1, and meta keywords
    • dTitle tag, CSS classes, and meta description
    Show the answer

    Answer: b · Title tag, H1, and meta description

    The title tag, H1, and meta description form the minimal set that communicates topical relevance and search result display to crawlers. CSS classes are a tempting distractor because they are HTML attributes, but the card explicitly flags extracting visual styling instead of semantic markup as a red flag.

    Read the full bite: What critical on-page SEO elements would you extract from HTML?

30. Question 30 of 30

    When using TF-IDF over the top-ranking pages for a query, what does a consistently high-scoring term most likely indicate?

    • aA distinctive topical term competitors cover that your draft may be missing
    • bA spelling error common across the corpus
    • cThe single most frequent word like 'the' in all pages
    • dA word to repeat until you hit a density percentage
    Show the answer

    Answer: a · A distinctive topical term competitors cover that your draft may be missing

    High TF-IDF means a term is frequent within documents yet rare across the broader corpus, marking distinctive topical vocabulary worth covering. Ubiquitous words like 'the' score low, and TF-IDF is about coverage, not stuffing to a density target.

    Read the full bite: Explain TF-IDF and its use in SEO analysis