How to Build a Source Page for Journalists That Actually Gets You Quoted

What most guides get wrong

Most guides treat a source page like a fancier LinkedIn profile. They obsess over polished prose, aspirational headlines, and a long narrative about your journey. That is exactly backwards.

A reporter working a story does not read narrative. They scan for proof and a usable quote. When your page buries your credentials under three paragraphs of storytelling, you have added friction at the precise moment friction loses you the citation.

The other common error is building a single page that tries to cover every topic you could possibly speak to. Journalists search by subject: 'estate planning attorney,' 'pediatric nutrition,' 'municipal bond risk.' A page that claims expertise in eight areas signals depth in none. Topical focus reads as credibility. Breadth reads as noise. Build for the search, not for the ego.

Why Do Most Expert Source Pages Never Get a Single Citation?

Most expert source pages never get a citation because they solve the wrong problem. They are designed to make the expert look impressive rather than to make the journalist's job easier. Those are not the same goal, and the gap between them is where citations get lost.

When I started studying how reporters actually source experts, a pattern became clear. A journalist on deadline moves fast and abandons any source that requires effort to verify. If they cannot confirm your role, your relevance, and your contact method within roughly thirty seconds, they move to the next name on their list. Your beautifully written origin story is not a feature to them. It is an obstacle.

There is also a discovery problem. Reporters find experts through databases, past coverage, colleague referrals, and increasingly through AI search tools that surface named experts on a topic. If your source page has no structured signals tying you to a specific subject area, you are effectively invisible to those discovery paths even if the page itself is well written.

Consider a securities litigation attorney. A reporter covering a fraud case needs to know three things immediately: that this person practices securities litigation, that they can speak on the record, and how to reach them before end of day. A page that leads with 'passionate about justice since law school' fails all three tests.

A page that leads with 'Securities litigation partner, available for comment on SEC enforcement and shareholder actions' passes them instantly. The failure is almost never a lack of expertise. It is a lack of packaging. The expert is genuinely qualified. The page just never presents that qualification in a form a working reporter can use under pressure.

Fixing the packaging, not the credentials, is where nearly all the improvement lives. This reframe changes everything downstream. Once you accept that the page is a tool for someone else's workflow, the layout, the copy, and the technical markup all follow logically from a single question: what does a reporter need, and how fast can I give it to them?

• Reporters abandon sources that take more than about 30 seconds to verify.
• Discovery happens through databases, past coverage, and AI search, not just your website.
• A narrative bio adds friction exactly when a journalist has none to spare.
• The problem is packaging, not a genuine lack of expertise.
• Topical relevance must be obvious in the first line, not the fourth paragraph.
• Every design choice should trace back to reducing the reporter's effort.

What Is the Deadline-First Layout and How Do You Build It?

The Deadline-First Layout is a page structure I use that orders every element by how urgently a journalist needs it. Instead of the standard bio-then-details flow, it front-loads the three things a reporter checks first and pushes everything else down. The layout has four zones, in this order. Zone one is the quotable angle. The first line states who you are in reporter terms and what you can speak to on the record.

Not 'award-winning financial planner' but 'Certified Financial Planner available for comment on retirement withdrawal strategies and inflation risk.' This single line does more work than any other element on the page because it answers the reporter's relevance question instantly. Zone two is fast verification. Directly beneath the angle, place linked credentials: your active license or bar number where public, your firm or institution with a link, and one or two pieces of prior coverage. These are the proof points a journalist needs to defend the citation to their editor. Every claim should be linkable, not just asserted. Zone three is contact and availability. State your preferred contact channel, your typical response time, and your general availability.

If you can turn around a comment in two hours, say so. Reporters route around slow sources, so publishing your responsiveness is itself a competitive signal. Zone four is depth. This is where topic pages, longer bio, publications, and speaking history live. A reporter who has already decided to use you will scroll here for supporting detail.

A reporter still deciding never needed it above the fold. The reason this works is that it matches the sequence of decisions a journalist makes: is this person relevant, are they credible, can I reach them in time, and do they have supporting depth. Each zone answers one question in the order the question arises.

When I apply this to a healthcare client, for instance, a pediatric endocrinologist's page opens with the conditions they can discuss, then their hospital affiliation and board certification with links, then their media contact and turnaround, then their peer-reviewed publications. A reporter working a childhood diabetes story can move from landing to sending an email in under a minute. That speed is the entire point.

• Zone 1: a quotable angle in reporter terms, stated in the first line.
• Zone 2: linked, verifiable credentials directly beneath the angle.
• Zone 3: preferred contact channel, typical response time, and availability.
• Zone 4: supporting depth like publications and full bio, placed last.
• Each zone answers one reporter question in the order it naturally arises.
• Publishing your response speed is a competitive advantage, not oversharing.

How Do You Build a Pull Quote Library That Reporters Actually Use?

A Pull Quote Library is the single most link-worthy element you can add to a source page, and almost no one includes it. It is a curated set of short, on-the-record statements organized by subtopic that a reporter can quote directly or use to frame their interview questions. Here is the logic.

When a journalist finds an expert, there is still work between 'this person is relevant' and 'I have a usable quote.' They have to reach you, wait for a reply, and hope the reply is quotable. A Pull Quote Library collapses that gap. It gives the reporter something immediately citable while you are still checking your inbox. Structure it by subtopic, not by chronology. For an estate planning attorney, subtopics might be trust versus will decisions, digital asset inheritance, and probate avoidance.

Under each, provide two or three tight statements written in a quotable voice: clear, specific, and free of hedging. Each statement should be attributable exactly as you want it printed, including your name and title. A few rules make this work in high-scrutiny fields. Every quote must be accurate and defensible, because a reporter may print it verbatim and you own the consequences.

Avoid absolute claims and keep the language precise. In regulated verticals like finance, legal, and healthcare, a sloppy pre-written quote is a liability, not an asset, so review them the way you would review anything published under your name. Mark the section clearly as available for attribution.

Something like: 'The following statements may be quoted directly with attribution to [name, title].' This gives the reporter explicit permission and removes any ambiguity about whether they need to confirm with you first. The compounding benefit is discovery. A well-structured Pull Quote Library gives AI search tools and journalist databases clean, topical, attributable text to surface.

When a reporter or an AI assistant searches for expert commentary on a subtopic, a page with organized quotable statements has far more to offer than a page with a paragraph of biography. In practice, I treat this section as a living document. Refresh the quotes when the news cycle or regulation shifts, so a reporter checking your page during a breaking story finds statements that speak to current conditions rather than last year's context. A stale quote library reads as neglect.

A current one reads as an expert who is engaged with their field.

• Organize quotes by subtopic, matching how reporters search for commentary.
• Write each statement to be printed verbatim, with exact attribution.
• Include an explicit permission line stating quotes may be attributed.
• Keep every quote accurate and defensible, especially in regulated fields.
• Refresh quotes as the news cycle or regulations shift.
• Clean, attributable text also helps AI search surface your commentary.

What Is the Verification Ladder and Why Does It Matter for Trust?

The Verification Ladder is a framework for organizing proof so a journalist can verify you to the exact depth their story requires. Different stories carry different scrutiny. A trend piece might need only your title and firm.

An investigative feature might need bar records, prior coverage, and a live confirmation call. Your page should support all of it. Think of verification as four rungs, each stronger than the last. Rung one is the named claim. Your exact role, title, and organization, stated plainly.

This is the minimum a reporter needs to attribute a quote correctly. Rung two is the linked credential. Every claim should link to independent evidence: your bar profile, your board certification registry, your faculty page, your firm bio. The reporter should never have to take your word for it. In YMYL fields, linkable credentials are the difference between a quotable expert and an unusable one. Rung three is prior coverage. Links to outlets that have already quoted you tell a reporter that other editors have vetted and trusted you. This is social proof in its most useful form: not a badge you awarded yourself, but evidence of prior editorial acceptance. Keep this section current so it never reads as dated. Rung four is real-time confirmation. Offer a fast, direct way to confirm anything live: a phone number, a scheduling link, or a stated turnaround for verification calls.

For a story under legal review, an editor may require speaking to you directly, and a page that makes that easy keeps you in the running when others drop out. The reason to structure verification as a ladder is that you never know which rung a given reporter needs. By building all four, you serve the quick trend piece and the heavily lawyered investigation from the same page. You remove the guesswork about how deep to go with credentials. One technical layer strengthens the whole ladder: Person schema with a sameAs property linking your professional profiles, credential registries, and prior coverage.

This helps search engines and AI tools connect your page to your verified expertise entity across the web. It is not a substitute for human-readable proof, but it reinforces every rung by making the connections machine-readable as well as visible to the reader. Build the ladder once and it works for every reporter, at every level of scrutiny, without you having to guess what they will ask for.

• Rung 1: your exact role, title, and organization, stated plainly.
• Rung 2: every credential linked to independent, verifiable evidence.
• Rung 3: links to prior coverage as evidence of prior editorial vetting.
• Rung 4: a fast, direct way to confirm details in real time.
• Different stories need different rungs, so build all four.
• Person schema with sameAs reinforces the ladder for search and AI tools.

Should You Build One Source Page or One Per Topic?

You should build one focused source page per distinct expertise domain, not a single page that lists everything you could possibly discuss. This runs against the common instinct to consolidate, but it aligns with how reporters actually find sources. Journalists search by subject.

A reporter working an immigration story searches for immigration expertise, not for your name. If your single page claims depth in immigration, tax, and personal injury, none of those searches sees you as a strong match, and the page dilutes its own topical relevance in the eyes of both search engines and human editors. A focused page concentrates every signal on one subject. The quotable angle, the Pull Quote Library, the prior coverage, and the schema all point at the same topic. That concentration is what makes the page rank for that topic and read as authoritative when a reporter lands on it.

Depth is a signal. Breadth dilutes the signal. Here is how I structure this in practice.

If an attorney genuinely practices in two distinct areas, say securities litigation and white-collar defense, they get two source pages, each fully built with its own Deadline-First Layout and its own quote library. A shared hub page can link to both for anyone browsing by name, but the topical pages do the ranking and citation work. There is a discipline required here. Only build a page for a topic you can genuinely support with credentials and prior work. A thin page on a topic you dabble in undermines the credibility of your strong pages.

In regulated fields especially, claiming expertise you cannot defend is a reputational and sometimes regulatory risk. Restraint is part of the strategy. The compounding benefit is that each focused page becomes an asset that accumulates authority over time.

As prior coverage grows and quotes refresh, a single-topic page deepens rather than spreads thin. Reporters covering that beat return to it. Search engines associate you more firmly with the subject.

AI search tools have a clean topical entity to surface. One deep page on a subject you own beats five shallow pages on subjects you touch. The swap test applies here too. If your page's content would make equal sense for a completely different profession, it is too generic to rank or to persuade an editor. Specificity to the topic, in language and in examples, is what separates a page reporters trust from a page they scroll past.

• Reporters and search engines both evaluate by subject, not by name.
• A focused page concentrates every signal on one topic, which reads as depth.
• Build separate full source pages for genuinely distinct expertise areas.
• Use a name-level hub page to link topical pages for browsers.
• Only build a page for a topic you can defend with real credentials and work.
• Focused pages compound authority over time rather than spreading thin.

How Do You Make Your Source Page Discoverable in Search and AI Tools?

You make a source page discoverable by giving both search engines and AI tools clean, structured signals that connect you to a specific expertise entity. A page can be beautifully written and still be invisible if machines cannot understand who you are and what you speak to. Start with Person schema.

Mark up your name, job title, organization, and, most importantly, the sameAs property. sameAs links your source page to your other verified profiles: your firm bio, your credential registry, your professional association listing, and prior coverage. This tells search engines that these entities are all the same person, which strengthens the association between you and your topic across the web. Next, align your URL, title, and headings with how reporters search.

The URL should include the topic and your professional role. The page title should read as a subject plus a source signal. Headings should use the natural-language questions a reporter or an AI assistant might ask, because AI search tools increasingly surface content that directly answers a phrased question.

The Pull Quote Library plays a discovery role too. Clean, attributable, topically organized text gives AI tools quotable material to surface when someone searches for expert commentary on a subtopic. A page structured as answer-first blocks is far easier for these tools to parse and cite than a wall of narrative prose. Do not neglect the basics that make the page reachable at all.

It should be crawlable, fast, mobile-readable, and internally linked from your site so it accrues authority rather than sitting orphaned. A source page hidden three clicks deep with no internal links is a page few will ever find. There is a nuance worth stating plainly. **Schema and structure do not manufacture authority.

They make real authority legible.** If the underlying credentials and coverage are not there, markup will not conjure them. But when the substance exists, structured signals ensure that search engines, journalist databases, and AI assistants can all connect the dots and route reporters to you. In my experience, the pages that get found combine three things: genuine topical depth, human-readable proof, and machine-readable structure.

Miss any one and the page underperforms. Get all three working together and the page compounds, becoming easier to find and more trusted every quarter it stays current. That combination, not any single trick, is what makes a source page a durable discovery asset rather than a static profile.

• Add Person schema with a sameAs property linking your verified profiles.
• Align URL, title, and headings with how reporters actually search.
• Phrase headings as natural-language questions for AI search tools.
• Structure content as answer-first blocks that are easy to parse and cite.
• Ensure the page is crawlable, fast, mobile-readable, and internally linked.
• Schema makes real authority legible; it does not create authority.

What I Wish I Knew Earlier About Source Pages

When I started building authority pages for experts in regulated fields, I over-invested in polish and under-invested in speed. I wrote elegant bios that read beautifully and got quoted rarely. What changed my approach was reframing the page as a tool for someone else's deadline. Once I stopped asking 'does this make my client look impressive' and started asking 'can a reporter act on this in under a minute,' the whole structure inverted. The angle moved up, the story moved down, and the proof became linkable rather than asserted. The second lesson took longer: a source page is not a launch-and-forget asset. The prior-coverage section ages, the quote library goes stale, and a reporter checking your page during a breaking story notices immediately. The pages that keep earning citations are the ones treated as living documents, reviewed each quarter. Authority here is not something you install once. It is something you maintain, and the maintenance is what compounds.

Your 30-Day Action Plan

1. Days 1-3 — Define your single strongest expertise topic and write your Zone 1 quotable angle in reporter terms.
2. Days 4-7 — Gather every credential and link its independent source: bar profile, board registry, firm bio, faculty page.
3. Days 8-12 — Collect links to all prior coverage and set a way for reporters to confirm details in real time.
4. Days 13-18 — Write your Pull Quote Library: two to three attributable statements per subtopic, plus a clear permission line.
5. Days 19-23 — Assemble the page using the Deadline-First Layout, ordering the four zones from angle to depth.
6. Days 24-27 — Add Person schema with sameAs, align URL and headings to reporter search language, and validate the markup.
7. Days 28-30 — Internally link the page, test load speed and mobile readability, and set a quarterly review reminder.

Frequently asked questions

What should the first line of a journalist source page say?

The first line should state who you are in reporter terms and exactly what you can speak to on the record. Skip the mission statement and lead with relevance: role, subject, and availability for comment. For example, 'Board-certified pediatric endocrinologist available for comment on childhood diabetes and growth disorders.' This single line answers the reporter's most urgent question, whether you are relevant to their story, before they read anything else. In my experience, sharpening this one line does more to earn citations than any other single change, because it works the way a reporter's attention actually works: fast, subject-first, and impatient with narrative.

How is a source page different from an About page?

An About page tells your story to a general audience. A source page is a working tool for a journalist on a deadline. The About page can be narrative, warm, and chronological. The source page must be answer-first, proof-forward, and built for speed. On a source page, your credentials are linked rather than described, your quotable angle leads rather than your journey, and your contact method and typical response time are visible rather than buried. Keep them as separate pages. When you blend them, the narrative slows the reporter down at exactly the moment they have no patience to spare, and the citation goes to a source who made verification easier.

Should I include pre-written quotes reporters can use directly?

Yes, a Pull Quote Library is one of the most useful and overlooked elements you can add. It gives reporters immediately citable statements organized by subtopic, collapsing the gap between finding you and quoting you. Two conditions matter. First, every quote must be accurate and defensible, because a reporter may print it verbatim and you own the consequences, which is especially critical in finance, legal, and healthcare. Second, include an explicit line granting permission to attribute the quotes to you by name and title. Keep the statements current as the news cycle and regulations shift, since a stale quote library reads as neglect while a current one signals an expert engaged with their field.

Do I need schema markup on a source page?

Person schema with a sameAs property is strongly worth adding because it connects your page to your verified expertise entity across the web. It links your professional profiles, credential registries, and prior coverage in a machine-readable way, helping search engines and AI tools associate you with your topic. That said, schema makes real authority legible; it does not create it. If the underlying credentials and coverage are not there, markup will not manufacture them. Add schema on top of genuine substance, validate that every sameAs URL resolves, and treat structure as an amplifier of proof rather than a substitute for it.

Is it better to build one source page or several topic-specific ones?

Build a focused page for each distinct expertise domain rather than one page covering everything. Reporters and search engines both evaluate by subject, so a page claiming depth in many areas dilutes its topical relevance and reads as shallow to a careful editor. Concentrate every signal, the quotable angle, the quote library, prior coverage, and schema, on a single topic. If you genuinely practice in two distinct areas, build two full pages and link them from a name-level hub. The discipline is to only build a page for a topic you can defend with real credentials and prior work. One deep page on a subject you own outperforms several thin pages on subjects you merely touch.

How often should I update my source page?

Review it at least quarterly. Two sections age fastest: prior coverage and your Pull Quote Library. A reporter checking your page during a breaking story notices immediately when your most recent coverage is two years old or your quotes reference outdated conditions. Set a recurring reminder to add new coverage links, refresh quotes against the current news cycle and any regulatory changes, and confirm that all credential and sameAs links still resolve. The pages that keep earning citations are treated as living documents, not launch-and-forget assets. In this field, authority is maintained rather than installed once, and the maintenance is precisely what compounds over time.