Person 1
Person 2
Person 3

50+ Happy Clients

Hi, I'm Nicolas!

Hi, I'm Nicolas!

Product Design

UX/UI Design

AI-Powered Products

Design Systems

Prototyping

✦ SCROLL DOWN ✦ AND KNOW ME BETTER
Profile Picture
✦ SCROLL DOWN ✦ AND KNOW ME BETTER
Profile Picture
✦ SCROLL DOWN ✦ AND KNOW ME BETTER
Profile Picture
Orange Pyramid
Purple Sphere
Purple Sphere
Blue Cylinder
Turquoise Star
Lime Green Object
Lime Green Object
Yellow Cube
Purple Cube
Purple Cube
Blue Pyramid
Blue Pyramid

About Me

I'm Nicolas, a product designer based in Northern Italy, near Lake Garda. My core is UX/UI: research, interaction design, interfaces people don't have to think about. On top of it I've built a second, deliberate specialty in AI-powered products: not using AI as a writing shortcut, but designing products where AI is part of what the product actually does.

My background is a little unconventional: I started in IT support, which turned out to be one of the best UX educations I could have asked for. Watching people struggle with confusing interfaces every day gave me a deep instinct for what makes a product frustrating versus effortless. That's the lens I bring to every project.

I'm Nicolas, a product designer based in Northern Italy, near Lake Garda. My core is UX/UI: research, interaction design, interfaces people don't have to think about. On top of it I've built a second, deliberate specialty in AI-powered products: not using AI as a writing shortcut, but designing products where AI is part of what the product actually does.

My background is a little unconventional: I started in IT support, which turned out to be one of the best UX educations I could have asked for. Watching people struggle with confusing interfaces every day gave me a deep instinct for what makes a product frustrating versus effortless. That's the lens I bring to every project.

I'm Nicolas, a product designer based in Northern Italy, near Lake Garda. My core is UX/UI: research, interaction design, interfaces people don't have to think about. On top of it I've built a second, deliberate specialty in AI-powered products: not using AI as a writing shortcut, but designing products where AI is part of what the product actually does.

My background is a little unconventional: I started in IT support, which turned out to be one of the best UX educations I could have asked for. Watching people struggle with confusing interfaces every day gave me a deep instinct for what makes a product frustrating versus effortless. That's the lens I bring to every project.

I ship what I design. On recent projects I've directed and executed full products end to end: architecture, interface, AI integration and release, working with AI as an execution partner while owning every design and product decision myself.

If you're building a digital product and want someone who thinks in UX/UI first and treats AI as a serious design material, let's talk.

I ship what I design. On recent projects I've directed and executed full products end to end: architecture, interface, AI integration and release, working with AI as an execution partner while owning every design and product decision myself.

If you're building a digital product and want someone who thinks in UX/UI first and treats AI as a serious design material, let's talk.

I ship what I design. On recent projects I've directed and executed full products end to end: architecture, interface, AI integration and release, working with AI as an execution partner while owning every design and product decision myself.

If you're building a digital product and want someone who thinks in UX/UI first and treats AI as a serious design material, let's talk.

Kind words from Clients

Testimonials

My Stack

Turquoise Cube

Framer revolutionizes my web design workflow. It goes beyond a simple website builder, offering a visual playground where I can craft stunning and interactive websites without getting bogged down in complex code.

Framer

Framer revolutionizes my web design workflow. It goes beyond a simple website builder, offering a visual playground where I can craft stunning and interactive websites without getting bogged down in complex code.

Framer

Tap to flip

Framer revolutionizes my web design workflow. It goes beyond a simple website builder, offering a visual playground where I can craft stunning and interactive websites without getting bogged down in complex code.

Framer

Tap to flip

Figma is my collaborative design platform of choice. I utilize it to work seamlessly with team members and clients, facilitating real-time feedback and design iterations. Its cloud-based approach streamlines the design process.

Figma

Figma is my collaborative design platform of choice. I utilize it to work seamlessly with team members and clients, facilitating real-time feedback and design iterations. Its cloud-based approach streamlines the design process.

Figma

Tap to flip

Figma is my collaborative design platform of choice. I utilize it to work seamlessly with team members and clients, facilitating real-time feedback and design iterations. Its cloud-based approach streamlines the design process.

Figma

Tap to flip

ChatGPT is my content generation and assistance tool. I leverage it for content ideas, copywriting, and problem-solving. It provides invaluable insights and suggestions that enhance the quality of my projects.

Chat GPT

ChatGPT is my content generation and assistance tool. I leverage it for content ideas, copywriting, and problem-solving. It provides invaluable insights and suggestions that enhance the quality of my projects.

Chat GPT

Tap to flip

ChatGPT is my content generation and assistance tool. I leverage it for content ideas, copywriting, and problem-solving. It provides invaluable insights and suggestions that enhance the quality of my projects.

Chat GPT

Tap to flip

HTML5 is the backbone of my web design work. I use it to structure content, ensuring that websites are semantically meaningful and accessible. It forms the foundation upon which the visual elements of a site are built.

HTML

HTML5 is the backbone of my web design work. I use it to structure content, ensuring that websites are semantically meaningful and accessible. It forms the foundation upon which the visual elements of a site are built.

HTML

Tap to flip

HTML5 is the backbone of my web design work. I use it to structure content, ensuring that websites are semantically meaningful and accessible. It forms the foundation upon which the visual elements of a site are built.

HTML

Tap to flip

CSS3 is my styling and layout powerhouse. It's instrumental in creating visually appealing websites by controlling everything from fonts and colors to the responsive design that adapts to various screen sizes.

CSS

CSS3 is my styling and layout powerhouse. It's instrumental in creating visually appealing websites by controlling everything from fonts and colors to the responsive design that adapts to various screen sizes.

CSS

Tap to flip

CSS3 is my styling and layout powerhouse. It's instrumental in creating visually appealing websites by controlling everything from fonts and colors to the responsive design that adapts to various screen sizes.

CSS

Tap to flip

I use a variety of other tools to enhance my workflow and adapt to your project’s needs.

Others

I use a variety of other tools to enhance my workflow and adapt to your project’s needs.

Others

Tap to flip

I use a variety of other tools to enhance my workflow and adapt to your project’s needs.

Others

Tap to flip

Services

01

Website Design & Development

01

Website Design & Development

Bring your vision to life with a website that’s both beautiful and functional. This service focuses on creating user-friendly designs that captivate visitors and drive key actions, whether it’s making a purchase, subscribing to your newsletter, or getting in touch. We take the time to understand your target audience, apply UX design principles for intuitive navigation and clear calls to action, and use the latest web technologies to deliver a website that looks great and performs seamlessly.

Red Pyramid

Landing pages are like digital magnets, built to grab attention and pull in leads or customers. We design pages that look great, say the right things, and get visitors to take action. From catchy headlines and stunning visuals to buttons people can’t help but click, we make sure your landing page works hard and delivers results.

Blue Cube

02

Landing Page Design

Your online store should feel like a breeze to shop in. We design e-commerce websites that look amazing, show off your products, and make it super easy for customers to browse, find what they need, and check out without a hitch. With clear product details, simple navigation, secure payments, and a smooth checkout, we help turn visitors into happy buyers.

Green Cylinder

03

E-commerce Design

Your website is an investment that needs care to keep thriving. We offer ongoing maintenance and support to keep it up-to-date, secure, and running like a dream. From software updates and security scans to performance checks and fixing any hiccups, we’ve got your website covered.

Orange Star

04

Website Maintenance & Support

Your website should feel like a natural part of your brand. We help create a cohesive brand identity, from logos and color schemes to fonts and design styles, making sure everything flows together. This consistency strengthens your brand’s presence and builds trust with your audience across all your digital platforms.

Blue Gem

05

Brand Identity Design

Keep your design consistent across all platforms. We create a design system with reusable components—UI elements, design patterns, and code snippets—that make the design and development process smoother. This ensures brand consistency and helps your team create new digital assets that fit perfectly with your existing website.

Pink Gem

06

Design System Creation

Put your users front and center in the design process. We do thorough user research and testing to understand your audience's needs, preferences, and challenges. This helps us optimize your website's user experience (UX), making it intuitive, easy to use, and focused on helping users reach their goals.

07

User Experience (UX) Research & Testing

Want to know more?

Want to know more?

We craft custom plans to fit your website's specific needs. Contact us for a quote!

We craft custom plans to fit your website's specific needs. Contact us for a quote!

Latest from the blog

What is the core difference between a Head of Product and a lead designer?

A Head of Product owns the "why" and the "what" at the organizational level: strategy, roadmap priorities, business outcomes, and cross team alignment. A lead designer owns the "how" within the design discipline: craft standards, design system decisions, and the quality of the design team's output. The Head of Product answers to the executive team for the product's commercial results. The lead designer answers to the Head of Product for the quality and consistency of the design work. One role carries P&L level accountability, the other carries craft and team leadership accountability. Both are senior, both are strategic, but only one sits in the room where budget, headcount, and product bets get decided.

What is the core difference between a Head of Product and a lead designer?

A Head of Product owns product strategy, roadmap priorities, and business outcomes across teams, while a lead designer owns design craft, team standards, and interface quality within the design function.

The distinction is structural, not hierarchical. A Head of Product sits at the intersection of business, technology, and user needs, and is accountable for whether the product wins in its market. A lead designer sits inside the design discipline and is accountable for whether the interfaces and experiences meet a defined quality bar.

In practical terms, the Head of Product decides which problems the company solves next quarter. The lead designer decides how those problems get solved at the interface level, and coaches the team to solve them consistently.

Dimension

Head of Product

Lead Designer

Primary accountability

Product strategy and business outcomes

Design quality and craft standards

Scope

Multiple product areas and teams

Design discipline and interface output

Key decisions

Roadmap, prioritization, resourcing, pricing input

Design system, patterns, UX flows, visual direction

Reports to

CPO, CTO, or CEO

Head of Product, Head of Design, or Design Director

Success metric

Revenue, retention, activation, market fit

Usability, consistency, design debt, team velocity

Stakeholder surface

Executives, sales, finance, customers

Product managers, engineers, designers, researchers

Where does the Head of Product's authority actually end?

A Head of Product's authority ends at the boundary of business strategy and team resourcing; the role does not typically dictate pixel level design decisions or individual craft choices.

This is the part that trips people up. The Head of Product sets the target outcome, defines the success metric, and clears the path. The lead designer defines the execution standard. When a Head of Product starts specifying button placement or component behavior, the role has drifted into design territory and usually signals a missing design lead.

The reverse also matters. A lead designer who negotiates roadmap priorities directly with the executive team without going through product leadership creates duplicated authority and confused accountability. Clear boundaries keep both roles effective.

Which skills does a Head of Product need that a lead designer usually lacks?

A Head of Product needs commercial fluency, portfolio prioritization, and stakeholder negotiation across finance, sales, and executives, which lead designers rarely develop inside the design discipline.

These are not soft extras. They are the operating skills of the role:

  • Business modeling: reading a P&L, building a business case, defending a product investment to finance.

  • Portfolio prioritization: deciding which of five competing initiatives gets funded and which gets killed.

  • Cross functional negotiation: aligning sales promises, engineering capacity, and support load into one coherent plan.

  • Market and competitive analysis: tracking positioning, pricing, and category shifts at a strategic level.

  • Hiring and org design: structuring product teams, defining career ladders, managing headcount across functions.

A lead designer typically builds deep expertise in interaction design, information architecture, design systems, and research synthesis. Those skills are essential, but they operate at a different altitude. A designer promoted into a Head of Product role without commercial training usually struggles in the first two quarters, because the job is no longer about craft quality.

How do the two roles collaborate on a real product decision?

A Head of Product and a lead designer collaborate by splitting the decision into a strategic layer owned by product and an execution layer owned by design, with explicit handoffs between them.

Take a concrete case: a SaaS company in Northern Italy wants to improve onboarding conversion in 2026. The Head of Product defines the target (raise activation from a baseline to a specific number), allocates engineering and design capacity, and sets the deadline. The lead designer defines the onboarding flow, runs usability tests, and owns the design system components used across the funnel.

The collaboration works when three things are explicit:

  1. Decision rights: who has the final call on scope, and who has the final call on craft.

  2. Feedback loops: weekly design reviews where product leadership sees work in progress, not just final screens.

  3. Shared metrics: both roles track the same activation and retention numbers, so design decisions stay tied to outcomes.

When those three are missing, the collaboration turns into rework and friction. When they are present, the Head of Product can defend the design investment to the executive team while the lead designer defends the quality bar to engineering.

Can a lead designer become a Head of Product?

A lead designer can become a Head of Product, but the transition requires building commercial, prioritization, and stakeholder management skills that design roles rarely teach directly.

The path exists and is increasingly common in startups, where design leaders often absorb product ownership as the company scales. The gap to close is rarely craft. It is usually:

  • Fluency in unit economics and pricing logic.

  • Comfort with saying no to well designed ideas that do not serve the business.

  • Experience running a roadmap with competing stakeholders, not just a design backlog.

  • Willingness to be measured on revenue and retention, not on design quality.

Designers who make the jump successfully usually spend a transitional period as a product manager or a design lead with explicit product ownership. Skipping that step tends to produce a Head of Product who still thinks like a craft lead and underinvests in the commercial side of the role.

Frequently Asked Questions

Does a Head of Product manage designers?

Usually not directly. A Head of Product manages product managers and works alongside design leadership. Direct management of designers typically sits with a Head of Design or Design Director, though in smaller companies the lines blur.

Is a Head of Product senior to a lead designer?

They sit at similar seniority but in different tracks. A Head of Product leads the product function; a lead designer leads the design function. Neither reports to the other in a well structured org, though both align on the same roadmap.

What does a lead designer do that a Head of Product never does?

A lead designer runs critique sessions, defines component behavior in the design system, conducts usability tests, and mentors designers on craft. A Head of Product rarely touches these activities because they belong to the design discipline.

Which role is more responsible for conversion focused design?

Both share it. The Head of Product sets the conversion target and prioritizes the work; the lead designer shapes the interface decisions that move the metric. Conversion focused design fails when either side treats it as the other's job.

How do the roles differ in a startup versus a scale up?

In a startup, one person often covers both scopes. In a scale up, the roles split cleanly: the Head of Product owns strategy and outcomes, the lead designer owns craft and design team standards. The split usually happens when the design team passes three to five people.

If you are mapping these roles inside your own team, start by writing down who owns the roadmap decision and who owns the design quality bar. That single exercise clarifies more than any org chart. For a deeper look at how design leadership and product strategy connect in practice, explore the rest of the work at Nicolas Benedetti.

Read article

Why do AI assistants quote some case studies and ignore others?

A design case study becomes quotable when you rebuild it as a structured answer page: a direct result statement in the opening, question based headings, self contained capsules under each heading, one comparison table, and schema markup that labels the work as a CreativeWork. Google AI Overviews, Perplexity and ChatGPT Search extract passages, not pages, so every section must survive on its own. In 2026 the winning format is a case study that reads like a documented answer to the question your client actually typed.

Why do AI assistants quote some case studies and ignore others?

AI assistants quote case studies that state a verifiable result inside the first sentence of each section, because retrieval pipelines score passages for standalone clarity.

Retrieval augmented generation splits your page into chunks, usually one heading plus the paragraphs beneath it. A chunk that opens with "the client wanted a refresh" carries no extractable fact. A chunk that opens with "the checkout redesign cut cart abandonment from 71% to 54% in eight weeks" gives the model a complete, attributable claim it can lift without context.

Three signals decide whether your passage gets cited:

  • Self sufficiency: the passage names the project, the metric and the timeframe without relying on earlier paragraphs.

  • Specificity: numbers, tools and dates beat adjectives. "Figma prototype tested with 12 users" outranks "user centered approach".

  • Structure: headings phrased as real questions match the query patterns people type into assistants.

Google's own guidance on helpful content rewards content written for people first, and passage level clarity is the practical expression of that principle for machine readers.

How do you structure a case study page with the capsule method?

The capsule method places a 120 to 150 character declarative summary directly under every question heading, followed by supporting evidence, so each block can be extracted whole.

Think of the page as a stack of independent answer blocks. Each block has three layers: the question heading, the capsule, and the proof. The capsule does the work of a snippet: one sentence, active voice, no pronouns pointing backward, no links inside it. The proof layer carries the detail, the screenshots, the before and after numbers.

Apply this sequence when you rebuild an existing case study:

  1. List the five to seven questions a prospective client would ask about the project.

  2. Turn each question into an h2 heading, written the way a person speaks.

  3. Write the capsule first, count the characters, cut until it fits the 120 to 150 range.

  4. Add 60 to 120 words of evidence under each capsule, with at least one concrete number.

  5. Move every comparison into a table and every process into a numbered list.

  6. Add FAQ schema and CreativeWork schema before publishing.

This structure also improves traditional SEO. Passage level clarity tends to lift dwell time because scanners find answers faster, and scanners are most of your traffic.

Which data should a quotable case study contain?

A quotable case study contains at least one baseline metric, one post launch metric, the measurement window and the tools used, because those four elements let an assistant verify the claim.

Design work is easy to describe and hard to prove. The fix is to publish the measurement frame alongside the outcome. If you ran a usability test, name the sample size. If you tracked conversion, name the analytics tool and the date range. A designer working as a freelancer in Italy or anywhere else competes on evidence, not on portfolio aesthetics.

Element

Weak version

Quotable version

Baseline

Low conversion

2.1% checkout conversion, January 2026

Outcome

Much better

3.4% checkout conversion, March 2026

Method

User research

12 moderated tests, Figma prototype, two rounds

Scope

Full redesign

Checkout flow only, 6 screens, 8 weeks

When a client forbids publishing numbers, publish the method and the qualitative finding instead. "Five of eight participants abandoned at the shipping cost step" is still a citable fact and it protects the relationship.

How do you write headings that match what people ask AI?

Headings match AI queries when they repeat the natural phrasing of a real question, such as "how long does a UX audit take" instead of "Methodology".

Assistants match your passage against the user's prompt. The closer your heading sits to that prompt, the higher the retrieval score. Pull the headings from your sales calls and your inbox: those are literal questions from buyers.

Useful patterns that work across design portfolios:

  • How long does the project take, and what happens in each phase?

  • What did the redesign change, measured in numbers?

  • Which tools and deliverables does the client receive?

  • What would you do differently on the next project?

The last one earns trust and gets quoted often, because honest retrospectives are rare in portfolio writing. Keep each heading under about 60 characters so it survives truncation in search results.

What technical markup makes a case study extractable?

Technical markup makes a case study extractable when the page carries Article or CreativeWork schema, FAQPage schema for the question section, and clean semantic HTML with one h1 and sequential h2 headings.

Structured data does not guarantee a citation, but it removes ambiguity about what the page contains. Google's structured data documentation lists the properties that matter for creative works: name, creator, datePublished, about and description. Fill them with the same facts that appear in the visible text, never with claims the page does not show.

Three practical rules for the markup layer:

  • Keep the FAQ answers in schema identical to the visible answers, word for word.

  • Use descriptive alt text on before and after screenshots so image results can surface them.

  • Avoid client side rendering for the main content, because some crawlers still read the raw HTML first.

Semantic HTML is the foundation. A page built from proper h2, p, ul and table tags is already machine readable before any schema is added.

How do you measure whether AI assistants cite your case study?

Citation tracking works by running a fixed set of prompts monthly across ChatGPT, Perplexity and Google AI Overviews, then logging which URLs appear and how often your case study is named.

Build a small prompt list from your buyer questions, run it on the first of every month, and record the results in a spreadsheet. Track three columns: prompt, assistant, cited URL. Over a quarter you will see which sections get pulled and which never surface.

Pair that with conventional signals: impressions and average position in Search Console for the question style queries, scroll depth on the case study page, and the number of inbound enquiries that mention a specific project. A case study that gets cited but never converts usually has a weak call to action, not a weak structure.

Iterate on the capsules that never get extracted. Rewrite them shorter, add a number, remove the pronoun. Small edits to a single passage often change citation behaviour within weeks.

Frequently Asked Questions

How long should a case study page be for AI citation?

Between 900 and 1,400 words works well, because the page needs enough distinct passages to cover several questions without diluting each one. Length matters less than the independence of every section.

Can I publish a case study without client permission for the numbers?

Publish the method and the qualitative findings instead, and anonymise the client as a sector description. Method details such as sample size and test rounds remain citable without exposing commercial data.

Does a portfolio image alone get quoted by AI assistants?

Rarely. Images support a claim but assistants extract text. Pair every visual with a caption that states the before and after outcome in one sentence.

Do I need a blog post and a case study for the same project?

No. One well structured case study page covers both intents when its headings answer the questions a blog post would raise. Duplicating the content splits authority across two URLs.

How often should a case study page be updated?

Review it every six months and refresh the dates, tools and metrics. A page that names 2026 in its measurement window signals current, verifiable work to both readers and retrieval systems.

Start with one project you already shipped. Rewrite its opening as a result statement, convert its headings into buyer questions, and add a capsule under each one. That single page will outperform a dozen image only portfolio entries in both search and AI answers, and it gives every future client a reason to trust the numbers before the first call.

Read article

How do AI search engines decide which sources to cite?

Writing articles that AI systems can cite with verifiable sources means leading every section with a self-contained answer, backing each claim with a named, linkable source, and structuring the page so a retrieval pipeline can extract one passage without reading the rest. Generative engines such as ChatGPT Search, Perplexity, Gemini and Google AI Overviews do not rank pages, they assemble answers from quotable fragments, so the unit of optimization in 2026 is the single sentence, not the whole article. The practical rule: if a sentence cannot survive being copied alone into another context, it will not be cited.

How do AI search engines decide which sources to cite?

Generative engines cite sources that are relevant to the query, quotable in isolation and authoritative enough to trust, scoring each passage before it enters an answer.

According to Locafy's guide to AI-citable content, a model composing an answer looks for material that meets those three criteria simultaneously, and most web content fails specifically on quotability because it is written to engage a human over time rather than to serve as a reference. The same source notes that AI models are trained to recognize question-and-answer patterns and frequently extract them verbatim, which is why FAQ blocks and definition blocks outperform narrative prose.

Ranktracker's analysis of evidence-backed content describes the underlying mechanism as a trust score built on factual stability, cross-domain confirmation, internal coherence, data provenance, timestamped truth and contextual integrity. In plain terms: the engine checks whether other trusted domains agree with you, whether your site contradicts itself, and whether your numbers match known data. Content that passes becomes the low-risk option, and AI systems consistently prefer low-risk sources.

What structure makes an article easy for AI to extract and quote?

An AI-citable article uses question-based headings, a direct answer in the first sentence of each section, and isolated blocks that stay meaningful when pulled out of the page.

The GEO analysis published by YouMark identifies three structural criteria that raise citation probability: clarity of structure with coherent H2 and H3 headings and easily isolable sections, authority signals such as content depth, internal links, external citations and recognizable authors, and verifiability with every technical claim attributed to a named source. It also recommends replacing generic descriptive headings with the real questions a prospect would type into a chat interface.

Concretely, the patterns that get extracted most often are:

  • Definition blocks that open a section with a one-sentence definition of the entity.

  • Comparison tables that place options side by side for "versus" queries.

  • Numbered steps where each step carries enough context to stand alone.

  • Data summaries grouping prices, timelines or benchmarks in one place.

  • Attributed expert statements tied to a named person and role.

Heading hierarchy works as the navigation system for retrieval. A heading that mirrors a real query tells the system exactly which block answers which question, while a heading like "Our Approach" gives it nothing to match against.

How do you write sentences that survive being quoted alone?

A quotable sentence states its subject explicitly, contains one specific verifiable claim, and makes complete sense when lifted out of the article and placed anywhere else.

This is the single most controllable factor in generative engine optimization. The test is mechanical: cover the rest of the page and read the sentence. If it needs the previous paragraph to make sense, rewrite it.

Weak, hard to cite

Strong, citable

"We respond quickly to requests."

"Average first response time is 47 minutes during business hours."

"Many factors affect pricing, so it depends."

"A standard audit costs between 2,000 and 5,000 euros depending on scope."

"This means the strategy works better."

"Question-based headings raise extraction rates because retrieval systems map headings to queries."

"Our platform is robust and streamlined."

"The platform processes 12,000 records per hour on a single node."

Two habits break quotability: opening key statements with dependent clauses ("Although many companies...") and using pronouns that point backward ("This approach...", "As mentioned above..."). Both force the model to keep reading, and a model that has to keep reading usually moves to a competitor's page instead. The Pixis content workflow applies the same principle at the editing stage: replace generic claims with the specific capability, finding or example the reader needs, and delete any sentence whose fact cannot be sourced.

Which sources count as verifiable for an AI pipeline?

A verifiable source is a named, dated, publicly reachable document that directly supports the specific claim it is attached to, ideally a primary source rather than a summary.

Not all evidence carries the same weight. Generative engines prioritize four categories: verifiable facts such as percentages, timelines and consensus definitions; recognized institutions and industry bodies; internal consistency across your own pages; and context that cross-references multiple angles. The Actian knowledge graph guide recommends a repeatable editorial check in which every factual claim is verified against primary sources, unsourced AI-generated statements are flagged or removed, and referenced sources are re-checked on a fixed cycle after publication, with a changelog recording data sources and publication dates for each page.

A practical sourcing checklist for each claim:

  1. Name the source in the sentence, not just in the link text.

  2. Attach the year, because undated data reads as stale to a timestamp-aware system.

  3. Prefer the primary document over an article describing it.

  4. Remove the claim entirely if no source exists, rather than softening the wording.

  5. Keep one definition per concept across the whole site so pages never contradict each other.

Does schema markup guarantee that AI will cite your page?

Schema markup helps machines understand a page but does not guarantee citation, because structured data makes content eligible for rich results without ensuring they appear.

Google states that structured data can make a page eligible for certain rich results but does not assure those results are shown, and the YouMark analysis makes the same point for generative answers: markup belongs inside a wider strategy, never as a standalone trick. The types that carry real value are Article and BlogPosting with author and publication dates, Organization for a clear entity definition, Person for author credentials, FAQPage only for questions genuinely present on the page, and HowTo for procedural guides. Markup that describes content not visible to the reader damages trust rather than building it.

Treat structured data as a consistency layer. It confirms what the page already says in clean prose, and clean prose is what actually gets quoted.

How do you build a page that becomes a recurring cited source?

A recurring cited source covers one topic territory with depth and continuity, linking pillar pages, comparisons, use cases and FAQs into a cluster that engines recognize as authoritative.

Authority in generative search is cumulative. Engines favor sources that preside over a subject with continuity, depth and coherence rather than publishing isolated posts. That means choosing a small number of strategic editorial territories, developing each over time, and connecting the pieces internally so the relationship between topics is visible. External mentions on industry media, reports and partner sites reinforce the same signal, because cross-domain confirmation is one of the checks described in the trust scoring model.

A workable cadence for 2026:

  • Publish one pillar page per territory with a full definition and data summary.

  • Add comparison and use-case articles that link back to the pillar.

  • Refresh statistics and dates on a fixed schedule, and record what changed.

  • Keep a public or internal changelog so provenance stays traceable.

Frequently Asked Questions

How long should the answer at the start of a section be?

Between 20 and 25 words, one sentence, stating the subject explicitly and delivering the answer before any context. This length fits cleanly into a synthesized response without truncation.

Do FAQ sections still help with AI citations?

Yes, but only when the questions are real and the answers are self-contained. FAQ blocks are not a shortcut to visibility in AI Overviews; they improve extraction because models recognize question-and-answer patterns and quote them verbatim.

Should I remove statistics I cannot source?

Yes. An unsourced number is a liability, because engines cross-check figures against known data and drop claims that fail confirmation. A shorter article with verified data outperforms a longer one with plausible but unverifiable figures.

How often should cited sources be re-checked?

A 90-day review cycle after publication is a reasonable baseline for pages carrying statistics or technical claims, with a changelog recording what was updated and when.

The takeaway is simple: write for extraction, source for verification, and structure for retrieval. If you want your articles quoted by ChatGPT, Perplexity and Google AI Overviews in 2026, start by auditing your existing pages section by section, rewriting each opening sentence as a standalone answer, and attaching a named, dated source to every number you keep.

Read article

Create a free website with Framer, the website builder loved by startups, designers and agencies.