How to Build an Author Website That Actually Works

A practical, strategic guide to building an author website as a system—not a collection of pages


Most author websites fail quietly.

They don't crash.
They don't look broken.
They don't throw errors or alerts.

They simply sit there, polite, tidy, and invisible, while their creators wonder why no one subscribes, clicks, or buys.

This is not because authors are lazy, untalented, or doing something "wrong."

It's because most website advice is built on the wrong assumptions.

This guide exists to correct that.

You'll learn how to build an author website as a decision system, not a design project—and how to use Claude and ChatGPT as strategic partners with distinct roles. The examples lean on Squarespace because it's stable and author-friendly, but the principles apply to any platform.

No hacks.
No hustle.
No fluff.


Why Most Author Websites Fail (and Why That's Not Your Fault)

Most advice aimed at authors quietly assumes:

  • You're promoting one book

  • You already understand SEO and funnels

  • Writing more content will fix visibility

  • Design matters more than structure

None of that is reliably true.

The real reason most author websites underperform is a lack of architecture.

Authors are told to "just build a site" the same way people are told to "just write a book." The result is predictable: effort without leverage.

An author website is not:

  • A digital business card

  • A bookstore

  • A prettier version of social media

It is:

  • A content hub you own

  • A trust-building system

  • A long-term discovery asset

Once you internalize that, every decision gets harder—but clearer.


The Core Mental Model: Think in Systems, Not Pages

Before touching Squarespace, WordPress, or any platform, you need the correct mental model.

Your website is a system with inputs and outputs.

Inputs

  • Books

  • Articles

  • Free resources

  • Search traffic

  • Pins, links, referrals

Outputs

  • Email subscribers

  • Reader trust

  • Sales (direct or indirect)

  • Long-term discoverability

Pages are just containers.

What matters is flow.

Every effective author website relies on four structural pillars.

  1. Structure – what exists

  2. Intent – why it exists

  3. Flow – how readers move

  4. Signal – what search engines understand

AI becomes useful only when it supports these pillars, not when it replaces them.


The Two-AI System: Claude for Structure, ChatGPT for Content

Most authors fail with AI because they use one tool for everything.

Claude and ChatGPT are not interchangeable.

  • Claude interrogates. ChatGPT executes.

  • Claude forces hard choices. ChatGPT smooths rough edges.

  • Claude catches loss aversion. ChatGPT generates options.

Claude's job: Architectural interrogation

  • Stress-test your structure before building

  • Catch hidden contradictions in your strategy

  • Force you to defend every page, every theme, every decision

  • Identify when you're optimizing for the wrong outcome

ChatGPT's job: Content production

  • Generate clean copy after the structure is locked

  • Maintain tone consistency across pages

  • Optimize for SEO and readability

  • Batch-process rewrites and schema markup

Critical rule: Never ask ChatGPT to validate your structure. It will agree with you. Claude won't.

Use Claude when you need strategic pushback.
Use ChatGPT when you need tactical efficiency.

Never reverse these roles.


Why Website Decisions Feel Irrationally Hard

If you've ever felt physical resistance to removing a page, that reaction is not intuition.

It's loss aversion.

Humans experience the pain of loss more intensely than the pleasure of gain. Pages feel "earned" simply because they took effort to create—even when they no longer serve a function.

This is why:

  • Authors keep pages they haven't touched in years.

  • Sites quietly bloat.

  • Clarity feels dangerous.

Structural decisions require you to ignore that signal.

The question is never, "What might I lose?"

The question is, "What measurably breaks if this disappears?"

If nothing breaks, the page is not structural. It's emotional.


Step 1: Decide What Your Website Is For (Before You Touch a Platform)

Most authors skip this step and regret it later.

You need three decisions, written down:

1. Primary audience (one, not many)

Not "readers."
Not "anyone interested in books."

One real, specific person you can picture.

2. Primary job (choose one)

  • Support book discovery

  • Drive email conversion

  • Establish authority

You may have secondary outcomes.

But only one job can be structural.

3. What your site does not do

Exclusions create clarity.

A website that tries to do everything convinces no one.

Tool pairing:

Use Claude first:

"Here's my draft purpose statement and three audience types I'm considering. Pressure-test this. Where am I hedging? What am I actually optimizing for?"

Claude will force you to choose. It won't let you hedge with "readers who might be interested in multiple things."

Then use ChatGPT:

Once Claude forces clarity, use ChatGPT to rewrite the final purpose statement in multiple tones and choose the clearest version.

If this feels uncomfortable, you're doing the right work.


Before Anything Else: The Minimum Viable Website Check

Before architecture matters, viability does.

If your site is slow or broken on mobile:

  • Discovery fails (pages don't load)

  • Conversion fails (forms don't render)

  • Authority fails (reading is frustrating)

Do this first:

  • Open your site on a phone

  • Check load speed and usability

If it fails, fix that before making structural decisions.

Clarity does not compensate for technical failure.


Many authors struggle with website design because they focus on appearance rather than structure. Our Author Website Checklist outlines the essential elements that help readers discover books and stay connected.


Step 2: Choose a Platform Based on Constraints, Not Trends

Platform debates are mostly noise.

What actually matters:

  • Stability

  • Ownership

  • Ease of updating

  • Predictable SEO behavior

  • Low maintenance overhead

Squarespace works well for many authors because it removes technical drag. WordPress works well if you're comfortable maintaining it.

The platform will not save you from bad structure.

Choose once.

Stop revisiting this decision.


Step 3: Stop Adding Pages. Start Removing Them.

Most author websites don't fail because they lack pages.

They fail because authors can't explain why pages exist.

The structural test is simple:

If I remove this page, what specifically breaks, and how would I notice?

If the answer is vague ("credibility," "professionalism," "just in case"), nothing breaks.

That page is not structural. It's clutter.

A working author website rarely needs over five core pages.

Anything beyond that must justify itself structurally, not emotionally.

Using Claude to Kill Pages (Not Preserve Them)

Claude is better at this than ChatGPT because it will argue with you.

Prompt:

"I have these 12 pages: [list them]. My primary job is [X]. Which pages exist only because of loss aversion? Be specific about what breaks, or doesn't break, if each disappears."

Claude won't reassure you. It will force you to defend each page structurally.

If you can't, the page dies.

ChatGPT will try to help you keep pages. Claude will help you kill them.


Step 4: Choose One Primary Job (and Subordinate the Rest)

Your website may do many things, incidentally.

It can only optimize for one.

Choosing a primary job does not eliminate the others; it subordinates them.

  • Discovery-first sites still collect emails

  • Conversion-first sites still sell books

  • Authority-first sites still get traffic

What changes is what everything serves.

When sites try to optimize for all three at once, readers hesitate, and hesitation kills action.

Tool pairing:

Use Claude:

"My site's primary job is [X]. Show me where my current structure optimizes for something else. What am I actually prioritizing based on my page hierarchy and CTAs?"

Claude will catch the contradictions you can't see.

Use ChatGPT:

Once your primary job is locked, use ChatGPT to rewrite CTAs, navigation labels, and page hierarchies to align with that single job.

You cannot evaluate architecture during the change.

This decision must be locked long enough to observe results.


Step 5: Design Content Architecture Before Writing Anything

Random blogging is the fastest path to burnout.

Instead, decide what you want to be known for.

Choose 2–3 core themes you can sustain for years.

For each theme:

  • One flagship article (deep, evergreen)

  • Supporting pieces that reinforce it

  • One relevant free resource (if conversion matters)

This creates:

  • Natural internal linking

  • Clear topical authority

  • Easier content planning

You are not writing more.

You are writing with intent.

Tool pairing:

Use Claude:

"I want to be known for [these three themes]. Which one has the clearest strategic moat? Which one am I keeping only because it feels safe?"

Use ChatGPT:

Once themes are locked, use ChatGPT to generate content outlines, heading structures, and FAQ sections for each flagship piece.


Step 6: Build Pages for Humans First, Search Engines Second

SEO is mostly clarity.

Every strong page has:

  • One primary topic

  • Logical structure

  • Clear headings

  • Internal links that make sense

  • A reason to exist

If a human is confused, Google will be too.

Tool pairing:

Use Claude to test clarity:

"Here's my draft page for [topic]. Where am I hedging? What's unclear? What assumption am I making that readers won't share?"

Use ChatGPT to execute improvements:

Once Claude identifies weak spots, use ChatGPT to:

  • Simplify language

  • Generate FAQ structures

  • Rewrite headings for scannable

  • Create meta descriptions

Do not use either tool to replace judgment.I


Step 7: Use Claude for Strategy, ChatGPT for Execution

Claude's strategic role: System design and decision pressure-testing

Claude excels at:

  • Structural interrogation—questioning whether pages justify their existence

  • Identifying hidden assumptions in your website strategy

  • Long-form strategic thinking—working through architecture decisions before building

  • Detecting loss aversion—catching when you're keeping pages for emotional reasons

  • Multi-turn strategic dialogue—building the system iteratively with pushback

When to use Claude:

  • Before building anything

  • When deciding what to remove

  • When your structure feels "off" but you can't explain why

  • When you need someone to argue with your choices

Example prompts:

"I'm keeping these seven pages. Which ones exist only because of loss aversion?"

"Here's my current architecture. What breaks if I remove [page Y]?"

"My site has three primary CTAs. Which one am I actually optimizing for based on placement and emphasis?"

ChatGPT's tactical role: Content execution and optimization

ChatGPT excels at:

  • Rapid content generation once the structure is locked

  • Tone consistency across multiple pages

  • SEO optimization—meta descriptions, heading structures

  • FAQ generation from existing content

  • Batch processing—rewriting multiple pages to match a voice

When to use ChatGPT:

  • After structural decisions are made with Claude

  • When you need to execute on a locked strategy

  • When you're optimizing existing content

  • When you need schema markup or technical SEO elements

Example prompts:

"Rewrite these five page titles to match this tone: [paste tone sample]"

"Generate FAQ schema markup for this page: [paste content]"

"Create three CTA variations optimized for email conversion"

Think of Claude as a strategic adversary and ChatGPT as a sharp junior editor.

Neither replaces your authority, lived experience, final judgment, or voice.


Step 8: Build for Longevity, Not Launch Hype

The most valuable author websites are boring in the best way.

They:

  • Improve instead of endlessly expanding

  • Update evergreen pages

  • Ignore trends unless they serve the system

Healthy cadence:

  • Quarterly content refresh

  • Annual structure review

  • Measure what matters (Search Console, not vanity stats)

Your website should work harder every year, not demand constant reinvention.


The Workbook: Free Author Website Clarity Kit

This article explains the system.

The workbook forces the decisions.

It includes:

  • A page survival test with real risk assessment

  • A binding choice between Discovery, Conversion, or Authority

  • A 90-day moratorium that prevents endless rebuilding

  • A tool decision matrix: Claude for structure, ChatGPT for execution

Download it only if you're willing to remove pages, lock a strategy, and stop tinkering for 90 days.

If you're looking for inspiration or ideas, this is not the right tool.


What to Do First If You're Overwhelmed

Ignore everything except this.

Week 1 Plan

Day 1–2: Define audience and primary job (use Claude to pressure-test)

Day 3: Choose platform and structure (use Claude to identify contradictions)

Day 4–5: Identify one flagship piece (use Claude to stress-test theme selection)

Day 6: Build core pages (use ChatGPT to generate clean copy)

Day 7: Publish imperfectly

Clarity comes from commitment—not preparation.


FAQ - Author Website

1. What makes an author website actually work?

An author website works when it has a single primary job, clear structural logic, and pages that exist only because something measurable breaks if they're removed. Working websites guide readers decisively instead of offering choices, avoid unnecessary complexity, and improve existing pages rather than endlessly expanding.

2. Do I need Squarespace or WordPress for an author website?

No platform will fix poor structure. Squarespace and WordPress both work if you can maintain them consistently. The right platform is the one that minimizes technical friction, so architectural decisions, not tools, determine success.

3. How do Claude and ChatGPT help with building an author website?

Claude helps by interrogating your structure, forcing hard decisions, and catching loss aversion before you build. ChatGPT helps execute content once strategy is locked, generates copy, optimizes for SEO, and maintains tone consistency. Never reverse these roles.

4. Can I build an author website without technical skills?

Yes. Most modern platforms allow authors to build functional websites without coding. Technical skill is rarely the limiting factor—unclear purpose, page bloat, and indecision are.

5. How many pages should an author website have?

Most effective author websites operate with five or fewer core pages. Any page beyond that must justify itself structurally. If removing a page doesn't break discovery, conversion, or access, it doesn't belong.

6. Does SEO still matter for author websites?

Yes, but only when paired with clarity. SEO works when pages have a single purpose, serve real reader intent, and are supported by internal linking and evergreen content. Keywords cannot compensate for structural confusion.

7. How long does it take for an author website to work?

Websites compound. With a locked structure and focused content, early signals often appear within a few months. Constant rebuilding resets momentum and delays results.

8. Should I use Claude or ChatGPT first?

Always use Claude first for structural decisions. Only use ChatGPT after the strategy is locked and you're ready to execute. Claude interrogates. ChatGPT generates. Never ask ChatGPT to validate your architecture.


Final Note

This system is designed to make you slightly uncomfortable.

If it doesn't, you probably didn't remove enough.


Valerie G Woods

I write evidence-based nonfiction for children, parents, and indie authors, focusing on clarity, practicality, and real-world results.

http://www.valeriegwoods.com
Next
Next

Gemini for Strategic Authors: The Chief Strategy Officer You Didn’t Know You Hired