Prompier
ApprovedDesign and mediawebsitearchitecture

Website sitemap and section plan for an organization

PL by Prompier Library ☆☆☆☆☆ New Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.

About this prompt

Produces a clear sitemap, section purposes and page priorities for an institution or organization website, based on its audiences and goals. Use it before briefing a designer or building a new site.

Prompt text

You are an information architect who plans websites around what visitors need to do. Your goal is a practical sitemap and section plan that a designer or web team can start from. Inputs - Organization and what it does: {{organization}} - Main visitor groups (for example prospective students, parents, donors, staff): {{audiences}} - Top goals for the website, such as enquiries, applications or donations: {{goals}} - Existing content or constraints, such as an old site or limited editors: {{constraints}} Steps 1. Restate the organization, audiences and goals in three lines and note any assumption you are making. Ask at most 3 clarifying questions only if a required input is missing; otherwise proceed. 2. For each audience, list the top five tasks they come to do and the questions they need answered. 3. Group the tasks into 5 to 8 top-level sections with plain labels a visitor would use. Avoid internal jargon. 4. Under each section, list the subpages needed and mark each as must-have for launch or later. 5. Decide what belongs in the header, the footer and the home page, and where the main call to action sits for each audience. 6. Check the plan: can each top task be reached in three clicks or fewer, and does every page have one clear purpose? Output format - Assumptions (bullets). - Audience task table: audience, top tasks, page that serves each. - Sitemap as an indented list, with must-have or later beside each page. - Home page blocks in order, one line each. - Content owners and updates: for each section, what needs regular updating. - Risks and open questions (max 5). Quality bar - Base labels on visitor tasks, not on the organization chart. - Do not invent facts about the organization; mark placeholders clearly. - Include accessibility basics in the notes: plain language, clear headings, readable contrast. - Keep the whole plan under 700 words.

Variables

4 variables
VariableWhat to enterExampleDefault
{{organization}}Your organization and what it doesHillside College, a small arts and design college—
{{audiences}}The main groups who visit the siteProspective students, parents, alumni, staff—
{{goals}}The top things the website should achieveMore applications and open day sign-ups—
{{constraints}}Existing content or limits, such as an old site or few editorsOld site with 200 pages, only two staff can edit—

Try it

Live preview
Your organization and what it does
The main groups who visit the site
The top things the website should achieve
Existing content or limits, such as an old site or few editors
Your finished prompt
You are an information architect who plans websites around what visitors need to do. Your goal is a practical sitemap and section plan that a designer or web team can start from. Inputs - Organization and what it does: {{organization}} - Main visitor groups (for example prospective students, parents, donors, staff): {{audiences}} - Top goals for the website, such as enquiries, applications or donations: {{goals}} - Existing content or constraints, such as an old site or limited editors: {{constraints}} Steps 1. Restate the organization, audiences and goals in three lines and note any assumption you are making. Ask at most 3 clarifying questions only if a required input is missing; otherwise proceed. 2. For each audience, list the top five tasks they come to do and the questions they need answered. 3. Group the tasks into 5 to 8 top-level sections with plain labels a visitor would use. Avoid internal jargon. 4. Under each section, list the subpages needed and mark each as must-have for launch or later. 5. Decide what belongs in the header, the footer and the home page, and where the main call to action sits for each audience. 6. Check the plan: can each top task be reached in three clicks or fewer, and does every page have one clear purpose? Output format - Assumptions (bullets). - Audience task table: audience, top tasks, page that serves each. - Sitemap as an indented list, with must-have or later beside each page. - Home page blocks in order, one line each. - Content owners and updates: for each section, what needs regular updating. - Risks and open questions (max 5). Quality bar - Base labels on visitor tasks, not on the organization chart. - Do not invent facts about the organization; mark placeholders clearly. - Include accessibility basics in the notes: plain language, clear headings, readable contrast. - Keep the whole plan under 700 words.

Sample output

Assumptions: a small community college; main audiences are prospective students and current students. Audience tasks | Audience | Top tasks | Page | | Prospective student | find programs, check fees, apply | Programs, Fees, Apply | | Current student | find timetable, get support | Student hub | Sitemap - Study here (must-have) - Programs A-Z (must-have) - Fees and funding (must-have) - Apply (must-have) - Student life (later) - Support (must-have) - About us (must-have) Home page blocks: headline with Apply button, popular programs, key dates, student stories, contact. Open question: who will keep the key dates page current?

An example the author shared. Your result will differ.

Reviews

No written reviews yet. If you have used this prompt, tell others how it went.