There is a small joke hidden inside one of the most familiar songs in America.

Yankee Doodle went to town,
Riding on a pony;
He stuck a feather in his cap
And called it macaroni.

The strange word is not feather. It is macaroni.

To us, macaroni is supper. To an eighteenth-century Englishman, it could mean something else entirely: a young man of extravagant taste, Continental manners, elaborate clothes, and an almost comic determination to appear sophisticated.

The joke, then, is not that Yankee Doodle confused a feather with pasta. The joke is that he confused an accessory with an identity.

He added one decorative flourish and imagined he had become fashionable.

That is also a surprisingly good description of bad SEO.

A business installs a plugin. It adds a few keywords. It publishes five generic FAQs. It pastes schema markup into the code. Someone changes the title tag and announces that the website is now “optimized for AI.”

A feather has been placed in the cap.

The underlying website, however, may still be slow, vague, repetitive, difficult to navigate, thin on evidence, and nearly useless to a prospective customer.

I call these macaroni fixes: visible signs of optimization that create the appearance of sophistication without improving the substance beneath them.

The phrase is new. The mistake is ancient.

The Song Has a Messier History Than We Remember

The history of “Yankee Doodle” does not arrive in one neat package.

The tune and title were circulating before the American Revolution. The Library of Congress[1] notes that musicologist Oscar Sonneck found a reference to “Yankee Doodle” in Andrew Barton’s 1767 comic opera The Disappointment. A Boston newspaper referred to the tune the following year.

But the famous pony-feather-macaroni verse is harder to pin down.

The earliest known surviving printed appearance of a familiar version appears in James Orchard Halliwell’s 1842 collection, The Nursery Rhymes of England[2]:

Upon a Kentish poney;
He stuck a feather in his hat,
And called him Macaroni.

That gap matters. The tune is securely tied to the eighteenth century. The best surviving print evidence for the verse most Americans know is nineteenth-century.

There is also the matter of authorship. A traditional story credits British army surgeon Richard Shuckburgh with composing the song during the French and Indian War. But modern accounts treat that attribution carefully. The Smithsonian[5] describes the song’s origins as uncertain, while Kate Van Winkle Keller’s essay for the Colonial Music Institute[3] distinguishes the early circulation of the tune from the later documentary trail of its lyrics.

The responsible conclusion is not dramatic:

  • The tune was circulating by the late 1760s.
  • British soldiers used versions of it to ridicule colonial Americans.
  • Americans adopted the song and turned the insult into a badge of identity.
  • The lyrics evolved.
  • The authorship remains disputed.
  • The famous macaroni stanza appears later in surviving print than many popular retellings imply.

Folklore wants a single author, a single date, and a single meaning.

History usually gives us a pile of fragments and asks us to behave ourselves.

The Macaroni Was a Performance

In eighteenth-century Britain, the Grand Tour was part education, part cultural pilgrimage, and part display of status. Wealthy young men traveled through Continental Europe and returned with new tastes in painting, architecture, food, language, clothing, and manners.

Some returned with more enthusiasm than restraint.

The word macaroni became associated with men who wore exaggerated fashions, cultivated affected behavior, and advertised their cosmopolitanism so aggressively that they became targets of satire. Peter McNeil’s study, “Macaroni Men and Eighteenth-Century Fashion Culture”[4], traces the macaroni through clubs, theater, clothing, social performance, and caricature. The Los Angeles County Museum of Art[6], the Library Company of Philadelphia[7], and the Museum of the American Revolution[8] all preserve examples of the visual stereotype: enormous hair, tiny hats, narrow silhouettes, ornate accessories, and poses designed to announce refinement.

Even the dictionary remembers the joke. Merriam-Webster[9] still includes the historical sense of macaroni as an affected young man or fop.

So imagine the colonial Yankee in the lyric.

He does not possess the education, travel, clothes, manners, or social standing associated with the macaroni. He has a pony and a feather. He believes the visible symbol will do the work of the invisible foundation.

That is what makes the line funny.

And that is what makes it useful.

What Is a Macaroni Fix?

A macaroni fix is an improvement that resembles optimization but does not materially strengthen the website.

It may be attractive. It may even be technically correct. But it is disconnected from the deeper work required to make the site useful, credible, discoverable, and persuasive.

Common examples include:

  • Adding keywords to weak copy without adding knowledge
  • Publishing nearly identical city pages and calling it local SEO
  • Installing structured data on pages with little visible substance
  • Replacing stock photography while leaving the site’s information architecture untouched
  • Rewriting title tags while ignoring the quality of the pages behind them
  • Publishing invented FAQs that no customer has actually asked
  • Producing large volumes of AI-assisted articles without first-party expertise
  • Chasing a special “AI search” tactic while core pages remain slow, thin, inaccessible, or hard to crawl

None of those actions is automatically useless.

A better title can improve presentation. Structured data can reduce ambiguity. A genuine FAQ can answer a real concern. Better photography can build trust.

The mistake is not using the feather.

The mistake is believing the feather is the hat.

AI Search Did Not Abolish the Fundamentals

Every technological shift produces a new vocabulary. AI-assisted search has given us AEO, GEO, AI SEO, LLM optimization, answer-engine optimization, and AI visibility optimization.

Some of these terms are useful. They help marketers describe new interfaces, new reporting problems, and new ways in which information may be summarized or cited.

But vocabulary has a dangerous side effect: it can make an old discipline sound obsolete before the replacement has been properly defined.

Google’s guidance is unusually plain. Its guide to optimizing for generative AI features[11] places the work inside the established discipline of SEO. Its documentation on AI features and websites[12] says there is no special AI schema or separate technical requirement that guarantees inclusion in AI Overviews or AI Mode.

A page still has to be found.

It still has to be crawled.

It still has to be indexed.

It still has to provide something worth retrieving.

That does not mean AI search changes nothing. It changes the shape of the opportunity.

People ask longer questions. Search systems synthesize information across sources. A useful paragraph, table, explanation, statistic, comparison, or definition may be extracted from the context of the full page and presented inside an answer.

That gives businesses more reason—not less—to create content that is:

  • Specific instead of generic
  • Clear enough to quote accurately
  • Supported by evidence
  • Connected to a recognizable business, author, or organization
  • Organized around genuine questions
  • Consistent with reliable information elsewhere
  • Valuable at both the page level and the passage level

AEO and GEO are not replacements for SEO.

They are reminders that the web increasingly rewards information that machines can understand and people can trust.

The foundation did not disappear. The rooms simply acquired more doors.

Eight Macaroni Fixes That Look Better Than They Work

1. Decorative Headings on Thin Content

A page can contain an H1, six H2s, a call to action, a testimonial slider, and 1,500 words—and still say almost nothing.

Thin content is not the same as short content. A 250-word page can be excellent when the question is narrow and the answer is complete. A 2,500-word page can be thin when it repeats generic claims without evidence, detail, or judgment.

A strong service page should explain:

  • What the service is
  • Who needs it
  • What problem it solves
  • How the process works
  • What the customer should expect
  • What limitations or tradeoffs exist
  • What proof supports the claims
  • What happens next

Headings organize expertise.

They do not manufacture it.

2. Keyword Stuffing Disguised as Local Relevance

A sentence does not become more relevant to Tyler, Texas, because the phrase “Tyler Texas SEO company” appears in it three times.

It becomes harder to read.

Google’s spam policies[15] identify unnatural repetition of keywords as a manipulative practice. But the more immediate problem is human. Customers can feel when copy has been written for a phrase instead of for them.

Modern relevance comes from coverage and meaning:

  • Services
  • Problems
  • Locations
  • Industries
  • Questions
  • Processes
  • Comparisons
  • Evidence
  • Outcomes

The goal is not to chant the keyword until the algorithm gives in.

The goal is to become the page that best explains the subject.

3. Metadata as a Substitute for Page Quality

Titles and meta descriptions matter. They help describe a page and may influence how it is presented in search.

But metadata is packaging.

Google may construct snippets from the page rather than use the supplied description word for word, as its guidance on search snippets[21] explains. Google has also said for years that it does not use the keywords meta tag[22] for web ranking.

A sharper label does not improve the product inside the box.

Fix the metadata.

Then fix the page.

4. Generic Images Where Proof Should Be

Stock photography can make a layout feel complete. It cannot show that the business has done the work.

The strongest visual assets are usually first-party:

  • Team photographs
  • Office or facility images
  • Before-and-after examples
  • Screenshots
  • Original diagrams
  • Product demonstrations
  • Project photography
  • Client-approved case-study visuals
  • Charts created from the company’s own data

Images should also be accessible. The W3C Alt Text Decision Tree[37] makes an important distinction: informative images need meaningful alternatives; decorative images may need empty alt attributes.

Alt text is not a hidden drawer for spare keywords.

It exists to communicate the purpose of the image.

5. Schema Markup on Pages That Do Not Deserve It

Structured data is useful because it gives machines standardized information about the visible content of a page. Google’s structured-data introduction[23] explains its role and limitations.

Depending on the page, useful types may include:

  • Organization[24]
  • LocalBusiness[25]
  • Article[26]
  • ProfilePage[27]
  • Product
  • Event
  • BreadcrumbList
  • VideoObject
  • FAQPage[28], where appropriate

Schema can clarify the name of the business, the author of an article, the location of a restaurant, the date of an event, or the relationship between a page and an organization.

It cannot turn shallow content into expertise.

There is no JSON incantation that makes an unhelpful page authoritative.

6. Duplicate Location Pages Mistaken for Expansion

The logic seems irresistible.

If one city page is good, twenty city pages must be twenty times better.

So a business copies the same service page, changes the city name, swaps one heading, and publishes the result across an entire region.

This creates the appearance of geographic reach without the evidence of geographic relevance.

Separate location pages make sense when they contain genuinely distinct information:

  • A real office
  • Local staff
  • Local reviews
  • Local projects
  • Different services
  • Area-specific requirements
  • Unique contact information
  • Original photography
  • Meaningful community involvement

When the only difference is the place name, the pages are not serving different users. They are serving a spreadsheet.

Google often handles similar pages through canonicalization and other systems, but the strategic problem remains: weak pages divide attention, dilute internal signals, and make the site harder to understand.

Expansion is not the number of URLs.

Expansion is the amount of useful territory the website can honestly cover.

7. Weak Internal Architecture

Some websites contain excellent information arranged like boxes in an attic.

The pages exist. Almost no one can find them.

Internal links help users and search engines understand:

  • Which pages matter most
  • How services relate
  • Which articles support which services
  • Where proof is located
  • What the next logical step should be
  • Which URL is the primary resource for a topic

Google’s SEO Starter Guide[17], its guidance on crawlable links[18], and its discussion of link architecture[19] all point toward the same basic idea: pages need pathways.

Descriptive anchor text is more useful than an endless field of “Learn More” buttons. A case study should link to the service it proves. A service page should link to related explanations, examples, questions, and next steps.

Internal linking is plumbing.

No one applauds it at the ribbon cutting.

Everyone notices when it fails.

8. Performance Theater

A site can appear fast during a client presentation and feel slow in the hands of an actual customer.

The difference is often context: device quality, connection speed, location, browser, third-party scripts, image weight, and what happens after the page first appears.

Google’s Core Web Vitals[32] and web.dev’s Web Vitals guidance[33] define the current good-experience thresholds as:

  • Largest Contentful Paint: 2.5 seconds or less
  • Interaction to Next Paint: 200 milliseconds or less
  • Cumulative Layout Shift: 0.1 or less

These are generally evaluated at the 75th percentile using real-user field data when enough data is available.

Performance is not the whole ranking system. A fast useless page remains useless.

But speed affects the customer before it affects the algorithm. Slow pages interrupt attention. Shifting layouts create mistakes. Delayed interactions make the site feel broken.

The business case is larger than SEO. In Rakuten 24’s Core Web Vitals case study[34], performance improvements were associated with gains in conversion and revenue per visitor. web.dev’s broader discussion of business impact[35] collects similar evidence.

A website is not fast because a developer says it is fast.

It is fast when users experience it that way.

From Macaroni Fixes to a Real Framework

The opposite of a macaroni fix is not a bigger checklist.

It is a system.

A strong website is not a collection of isolated optimizations. It is an organized body of evidence: useful pages, clear relationships, recognizable authorship, credible claims, accessible design, reliable performance, and measurable business outcomes.

Here is the order that usually matters.

1. Build Definitive Service Pages

The central service pages should be the clearest explanation of what the business actually does.

A definitive page answers the questions a serious buyer asks before making contact:

  • Is this for a company like mine?
  • What exactly is included?
  • What makes this process different?
  • How long does it take?
  • What does success look like?
  • What might prevent success?
  • What proof is available?
  • Who will do the work?
  • What should I do next?

This is where many websites fail. They describe the category rather than the company.

A law firm page explains what personal injury law is but not how the firm handles a case. A restaurant says it offers private dining but does not explain room capacities, menus, deposits, timing, or accessibility. A marketing agency promises growth but does not show its process, decisions, work, or measurement.

Generic information establishes the topic.

Specific information establishes the business.

2. Add Proof That Could Not Belong to Anyone Else

First-party proof is difficult to fake because it emerges from actual experience.

Useful proof includes:

  • Named case studies
  • Original data
  • Process screenshots
  • Before-and-after comparisons
  • Client-approved results
  • Staff credentials
  • Project photography
  • Demonstrations
  • Detailed testimonials
  • Lessons learned
  • Honest limitations

Google’s guidance on helpful, reliable, people-first content[13] emphasizes originality, trust, and value to the intended audience. Its advice on succeeding in AI search[14] similarly encourages useful, distinctive content rather than commodity material.

AI can help organize knowledge.

It cannot manufacture the experience the company never had.

3. Build a Knowledge Architecture

A website should not merely contain pages. It should explain how its knowledge fits together.

A strong architecture usually connects:

  • A main capability page
  • Individual service pages
  • Industry pages
  • Location pages where justified
  • Case studies
  • Team profiles
  • Frequently asked questions
  • Comparison articles
  • Process explanations
  • Supporting research
  • Conversion pages

The structure should make sense to a person before it is optimized for a crawler.

A visitor should be able to move from a broad question to a specific answer, from an answer to proof, and from proof to action.

That pathway is also what makes the site easier for search systems to interpret.

4. Use Structured Data Precisely

Once the visible information is strong, structured data can make important facts explicit.

Use it to identify:

  • The organization
  • The local business
  • Authors and team members
  • Articles
  • Events
  • Products
  • Breadcrumbs
  • Videos
  • Frequently asked questions where the format and guidelines fit

Connect entities carefully. Schema.org’s sameAs[31] property can point to authoritative external pages that identify the same person or organization.

But the markup must match the page.

Do not add reviews that users cannot see. Do not mark ordinary sales copy as an FAQ. Do not claim an author who did not write or review the article. Do not create a richer machine description than the human page deserves.

Structured data should reduce ambiguity.

It should not increase fiction.

5. Improve Mobile Usability, Accessibility, and Performance

Google uses mobile-first indexing, which means the mobile version of the content is central to how the site is understood. Its mobile-first indexing best practices[20] stress content and metadata parity.

But this is not merely a Google problem.

Most customers do not experience the website on the designer’s monitor. They experience it on a phone, with one hand, in a parking lot, under bad lighting, while distracted.

That environment changes the standard.

Buttons must be easy to tap. Text must be readable. Forms must be usable. Navigation must be obvious. Images must not push the layout around. Important information must not disappear on mobile.

Accessibility belongs in the same conversation because clarity, semantics, keyboard support, contrast, labels, and image alternatives improve the site for more people and often make the underlying information easier for machines to interpret.

6. Measure Outcomes Instead of Applause

The final macaroni fix is measurement theater: reporting impressions, rankings, or AI mentions without connecting them to the business.

Visibility matters.

But visibility is not the end of the story.

A serious measurement plan should track actions such as:

  • Form submissions
  • Phone calls
  • Reservation clicks
  • Consultation requests
  • Quote requests
  • Purchases
  • Qualified leads
  • Event registrations
  • Direction requests
  • Email signups

Google Analytics allows important actions to be marked as key events[40]. Search Console and Analytics can also be evaluated together[41] so that search exposure is compared with behavior and conversion.

In June 2026, Google also introduced dedicated generative-AI performance reporting in Search Console[39]. That creates a new layer of visibility data.

It does not change the final question.

Did the website help the right person take the right action?

A Better Order of Operations

When a website needs improvement, the sequence matters.

First: Audit Reality

Find out what exists.

Review:

  • Indexability
  • Crawl paths
  • Canonical URLs
  • Duplicate or overlapping pages
  • Mobile parity
  • Internal links
  • Page templates
  • Structured data
  • Core Web Vitals
  • Accessibility problems
  • Conversion tracking
  • Content quality
  • Proof and authorship
  • Business-profile consistency

Do not begin with the most fashionable tactic.

Begin with the largest obstacle.

Second: Repair the Core Pages

Strengthen the pages closest to revenue and customer decisions:

  • Homepage
  • Main service pages
  • Location pages
  • Product or menu pages
  • Contact and conversion pages
  • About and team pages
  • High-value landing pages

These pages form the commercial spine of the website.

Third: Add Proof and Supporting Knowledge

Build the material that makes the claims believable:

  • Case studies
  • Original FAQs
  • Comparisons
  • Process explanations
  • Staff profiles
  • Project examples
  • Research
  • Original imagery
  • Testimonials with useful detail

Fourth: Improve the Connections

Clarify navigation, breadcrumbs, internal links, related content, canonicalization, sitemaps, and structured data.

A strong page becomes more valuable when the rest of the site explains what it means.

Fifth: Validate

Use the tools designed to catch mistakes:

  • Search Console
  • Rich Results Test
  • Schema validators
  • PageSpeed Insights
  • Lighthouse
  • Mobile and browser testing
  • Accessibility testing
  • Analytics debugging

Sixth: Measure and Revise

Look for:

  • Qualified organic traffic
  • Growth in relevant queries
  • Conversions
  • Assisted conversions
  • Engagement with high-value pages
  • Local actions
  • Search and AI visibility
  • Revenue or lead quality

Then revise the site based on evidence.

SEO is not something applied once.

It is the maintenance of a useful public record about the business.

What the Feather Really Means

The feather was not the problem.

A feather can complete a well-made hat.

A title tag can improve a strong page. Schema can clarify a real entity. An FAQ can answer a real question. A beautiful image can strengthen a credible story.

The problem begins when the visible flourish is asked to carry weight that belongs to the structure beneath it.

That is the lesson hidden in “Yankee Doodle.”

The colonial rider understood the symbol of sophistication but not the system that gave the symbol meaning.

Websites make the same mistake when they display the outward signs of optimization without doing the slower work of becoming useful, specific, trustworthy, accessible, and measurable.

The goal is not to make a website look optimized.

The goal is to make it useful enough to rank, credible enough to trust, clear enough to quote, and persuasive enough to generate business.

That is the difference between a feather and a framework.

And it is the difference between calling something macaroni and knowing what macaroni means.

Sources