{"id":470,"date":"2026-10-09T09:10:27","date_gmt":"2026-10-09T09:10:27","guid":{"rendered":"https:\/\/push.digital\/blog\/?p=470"},"modified":"2026-10-31T07:07:24","modified_gmt":"2026-10-31T07:07:24","slug":"website-planning-process","status":"publish","type":"post","link":"https:\/\/push.digital\/blog\/website-planning-process\/","title":{"rendered":"Behind the Scenes: The Website Planning Process Before We Build Anything"},"content":{"rendered":"\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#what-actually-happens-before-anyone-touches-a-design-tool\">What Actually Happens Before Anyone Touches a Design Tool<\/a><\/li><li><a href=\"#what-is-the-website-planning-process-step-by-step\">What Is the Website Planning Process, Step by Step?<\/a><ul><\/ul><\/li><li><a href=\"#the-brief-where-most-of-the-real-decisions-get-made\">The Brief: Where Most of the Real Decisions Get Made<\/a><\/li><li><a href=\"#sitemap-and-information-architecture-are-not-the-same-thing\">Sitemap and Information Architecture Are Not the Same Thing<\/a><\/li><li><a href=\"#planning-for-chennai-and-tamil-nadu-businesses-specifically\">Planning for Chennai and Tamil Nadu Businesses Specifically<\/a><\/li><li><a href=\"#what-happens-when-planning-gets-skipped\">What Happens When Planning Gets Skipped<\/a><\/li><li><a href=\"#how-long-does-website-planning-actually-take\">How Long Does Website Planning Actually Take?<\/a><\/li><li><a href=\"#conclusion\">Conclusion<\/a><\/li><li><a href=\"#frequently-asked-questions\">Frequently Asked Questions<\/a><ul><li><a href=\"#faq-question-1791535338723\">What is the website planning process?<\/a><\/li><li><a href=\"#faq-question-1791535374326\">How long does website planning take before design starts?<\/a><\/li><li><a href=\"#faq-question-1791535381210\">What is included in a website brief or discovery phase?<\/a><\/li><li><a href=\"#faq-question-1791535390938\">What&#8217;s the difference between a sitemap and information architecture?<\/a><\/li><li><a href=\"#faq-question-1791535403219\">Why is website planning important before development?<\/a><\/li><li><a href=\"#faq-question-1791535413657\">What questions should a business answer before building a website?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Most website conversations start the wrong way. A business owner calls an agency, mentions a few pages they want, and asks how soon design can start. <strong>The website planning process<\/strong> is what happens before that question can be answered honestly, and skipping it is the single biggest reason redesigns run over budget and over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Key Takeaway:<\/strong> Proper planning before a website is built covers goals, structure, content, and technical requirements before a single screen is designed. It exists because design decisions made without this groundwork usually get undone mid-project, once, when the missing information finally surfaces.<\/p>\n\n\n\n<h2 id=\"what-actually-happens-before-anyone-touches-a-design-tool\" class=\"wp-block-heading\">What Actually Happens Before Anyone Touches a Design Tool<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas-1024x576.avif\" alt=\"A blank laptop design canvas next to printed sitemap pages\" class=\"wp-image-472\" srcset=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas-1024x576.avif 1024w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas-300x169.avif 300w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas-768x432.avif 768w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas-1536x864.avif 1536w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas-960x540.avif 960w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-blank-canvas.avif 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Clients often picture website work as a straight line: brief, design, build, launch. In practice, the planning stage is where most of the real decisions get made, and design is where they get expressed visually. A logo gets picked in an afternoon. Deciding what a visitor needs to see first, second, and never takes longer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is also where most agencies and most clients disagree without realising it. The client wants to see something. The agency knows that showing a homepage mockup before the sitemap is settled means redoing that homepage later, because the sitemap usually changes once content and structure are worked through properly. Push Digital has been building brands out of Chennai for more than 25 years. The pattern that repeats across that time is simple: projects that skip planning don&#8217;t actually save time. They just move the delay to a later, more expensive stage of the project, usually once design or development is already underway.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A well-run planning phase produces four things before design starts. A written goal for the site. A full page structure. A content plan with who writes what. A technical checklist covering hosting, forms, and basic SEO setup. Nothing visual yet. That is deliberate, and it is the part most clients find hardest to sit through, because there is nothing to look at and approve.<\/p>\n\n\n\n<h2 id=\"what-is-the-website-planning-process-step-by-step\" class=\"wp-block-heading\">What Is the Website Planning Process, Step by Step?<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check-1024x576.avif\" alt=\"Four-stage website planning process diagram from goals to technical readiness\" class=\"wp-image-473\" srcset=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check-1024x576.avif 1024w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check-300x169.avif 300w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check-768x432.avif 768w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check-1536x864.avif 1536w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check-960x540.avif 960w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-4-stage-check.avif 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The website planning process moves through four stages: defining the goal and audience, mapping the site structure, planning the content, and setting the technical requirements. Each stage produces a document the next stage depends on, which is why skipping one usually means redoing the ones that follow it.<\/p>\n\n\n\n<h3 id=\"stage-1-goals-and-audience\" class=\"wp-block-heading\">Stage 1: Goals and Audience<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before any page gets named, the brief has to answer two questions plainly: what is this website for, and who is it actually talking to. A B2B manufacturer selling to procurement managers needs a different homepage than a retail brand selling direct to consumers on their phones. Vague answers here (&#8220;we want more leads&#8221;) get narrowed down into something a sitemap can be built against (&#8220;we want procurement managers to download a spec sheet without talking to sales first&#8221;).<\/p>\n\n\n\n<h3 id=\"stage-2-sitemap-and-information-architecture\" class=\"wp-block-heading\">Stage 2: Sitemap and Information Architecture<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">With the goal set, the structure gets mapped: every page the site needs, how they connect, and what a visitor does on each one. This is covered in more detail below, because it is the stage most planning guides compress into a single bullet point and the one that causes the most rework when rushed.<\/p>\n\n\n\n<h3 id=\"stage-3-content-plan\" class=\"wp-block-heading\">Stage 3: Content Plan<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pages without content are placeholders. The content plan assigns who writes what, in what order, and by when, because a design built around &#8220;lorem ipsum&#8221; text almost always looks different once real sentences replace it. Real copy runs longer or shorter than the mockup assumed.<\/p>\n\n\n\n<h3 id=\"stage-4-technical-and-seo-readiness\" class=\"wp-block-heading\">Stage 4: Technical and SEO Readiness<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The last stage before design covers the parts that are invisible until they go wrong: domain and hosting setup, form handling, analytics tracking, and basic on-page SEO structure (title tags, meta descriptions, URL patterns). None of it is glamorous. All of it is expensive to retrofit after launch.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Push Digital&#8217;s 4-Stage Website Planning Check<\/strong> is the recommended sequence for any team about to start a website project, whether they are working with an agency or in-house:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Write the website&#8217;s single primary goal in one sentence, and name the one audience it serves most<\/li>\n\n\n\n<li>Map every page and the one action each page should drive, before naming any visual direction<\/li>\n\n\n\n<li>Assign content ownership per page, with a delivery date for each<\/li>\n\n\n\n<li>List every technical dependency: hosting, domain, forms, analytics, basic SEO fields<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Each item on this check produces a document the design stage can be built against, instead of a design stage that produces the documents after the fact.<\/p>\n\n\n\n<h2 id=\"the-brief-where-most-of-the-real-decisions-get-made\" class=\"wp-block-heading\">The Brief: Where Most of the Real Decisions Get Made<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Take a mid-sized logistics company planning its first proper website in years. The old site was built around a service list nobody had updated since a previous rebrand. The brief conversation surfaces something the client hadn&#8217;t said out loud. Half their new business now comes from a referral that lands directly on the &#8220;About&#8221; page, not the homepage. That page currently has three sentences on it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That detail changes the sitemap. It also changes which page gets the most content budget, and it often points to a gap in how the brand itself is being presented, which is a <a href=\"https:\/\/push.digital\/#services\">branding and visual identity<\/a> question as much as a website one. None of this comes from a template brief form with ten generic fields. It comes from asking what actually drives business for this specific company, and then checking that answer against what the current site shows a visitor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A good website brief is not a form to fill in once. It is a working document, revised as the planning stage surfaces things the client did not think to mention upfront. A competitor audit reveals a gap. A sitemap exposes another, once pages are actually laid out side by side. The brief absorbs all of it before design starts, not after.<\/p>\n\n\n\n<h2 id=\"sitemap-and-information-architecture-are-not-the-same-thing\" class=\"wp-block-heading\">Sitemap and Information Architecture Are Not the Same Thing<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia-1024x576.avif\" alt=\"Table comparing a website sitemap to information architecture by function and risk\" class=\"wp-image-474\" srcset=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia-1024x576.avif 1024w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia-300x169.avif 300w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia-768x432.avif 768w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia-1536x864.avif 1536w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia-960x540.avif 960w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-sitemap-vs-ia.avif 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A sitemap lists the pages a website will have. Information architecture decides how those pages relate to each other and to the visitor&#8217;s task, which is why the two get confused constantly and why confusing them causes navigation problems later. A sitemap with fifteen well-named pages can still have broken information architecture if a visitor cannot find the one page they actually came for in two clicks or fewer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/seo-starter-guide\" target=\"_blank\" rel=\"noopener\">Google&#8217;s own guidance on site structure<\/a> treats a clear, crawlable hierarchy as a foundation for both usability and indexing. Getting this stage right once avoids a navigation rebuild later, touching every page template rather than one page&#8217;s content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In practice, information architecture work means grouping pages by what a visitor is trying to do, not by how the business is internally organised. A manufacturing company might have a Sales department, a Service department, and an Engineering department, but a visitor researching a problem does not think in those terms. They think in terms of the problem they have. The sitemap gets built around that, and the internal departments get mapped onto it afterward, not the other way round.<\/p>\n\n\n\n<h2 id=\"planning-for-chennai-and-tamil-nadu-businesses-specifically\" class=\"wp-block-heading\">Planning for Chennai and Tamil Nadu Businesses Specifically<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A website planning process written for a generic global audience misses details that matter for businesses operating out of Chennai and Tamil Nadu specifically. Review cycles often run across more stakeholders than a Western small business would involve. WhatsApp frequently sits alongside email as a primary client communication channel. Bilingual or Tanglish content decisions need to be made at the planning stage, not bolted on after design is already approved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Local sectors carry their own planning quirks too. A textile or jewellery showroom in T. Nagar usually needs the sitemap built around high-resolution product imagery and a straightforward enquiry path, not a blog-heavy structure. An IT services company on OMR, selling to clients outside India, carries a different weight entirely. A visitor&#8217;s first impression of the site matters more than it would for a locally known brand, simply because there is no existing reputation to lean on before that first page loads.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">None of this changes the four-stage structure. It changes what gets prioritised inside each stage, and that prioritisation is exactly what a generic planning checklist cannot give a Chennai business. It is also visible in how finished sites for different sectors actually turn out once planning is done properly, which is worth seeing in <a href=\"https:\/\/push.digital\/#works\">our portfolio<\/a> rather than describing in the abstract.<\/p>\n\n\n\n<h2 id=\"what-happens-when-planning-gets-skipped\" class=\"wp-block-heading\">What Happens When Planning Gets Skipped<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Picture a retail chain that skips straight to design because the owner wants to see something quickly. The homepage gets approved in a week. Three weeks later, during the content stage, it becomes clear that the &#8220;Shop&#8221; page the design assumed needs twelve product categories, not the four the homepage layout was built around. The homepage gets redesigned. The timeline that was meant to save three weeks now runs six weeks longer than a planned project would have.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Without Planning<\/th><th>With Planning<\/th><\/tr><\/thead><tbody><tr><td>Sitemap decided during design, revised mid-build<\/td><td>Sitemap finalised before design starts<\/td><\/tr><tr><td>Content written to fit an existing layout<\/td><td>Layout built to fit planned content<\/td><\/tr><tr><td>SEO and technical setup addressed after launch<\/td><td>Technical requirements listed before design<\/td><\/tr><tr><td>Stakeholder feedback arrives late, forces rework<\/td><td>Feedback gathered during the brief, before cost is sunk<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The pattern holds across most unplanned projects: the stage that gets skipped resurfaces later, at a point in the project where fixing it costs more than planning for it would have. A content gap discovered during design means redesigning. A technical requirement discovered after launch means rebuilding parts of the site that are already live, often while the client is trying to use the site for the exact purpose it was built for.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is not an argument for planning everything down to the last pixel before anything else happens. Some decisions genuinely do get made better once a design is in front of people, because a mockup makes a vague idea concrete in a way a document cannot. The distinction that matters is which decisions those are. Visual style, tone of imagery, and layout preference are reasonable to leave until the design stage. What page the site needs, what each page is supposed to accomplish, and who writes the words on it are not, because every one of those decisions changes the shape of the design itself.<\/p>\n\n\n\n<h2 id=\"how-long-does-website-planning-actually-take\" class=\"wp-block-heading\">How Long Does Website Planning Actually Take?<\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline-1024x576.avif\" alt=\"Timeline showing website planning taking two to six weeks based on review speed\" class=\"wp-image-475\" srcset=\"https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline-1024x576.avif 1024w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline-300x169.avif 300w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline-768x432.avif 768w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline-1536x864.avif 1536w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline-960x540.avif 960w, https:\/\/push.digital\/blog\/wp-content\/uploads\/2026\/10\/website-planning-process-timeline.avif 1672w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Website planning typically takes two to six weeks before design work begins, depending on how many stakeholders need to sign off and how much of the content already exists. A five-page business site with one decision-maker moves through planning faster than a fifty-page site with multiple departments reviewing each stage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The variable that moves this timeline most is not the website&#8217;s size. It is how quickly stakeholders respond to review requests. A sitemap sent for approval on a Monday and reviewed the same week keeps the project moving. The same sitemap sitting in an inbox for two weeks adds two weeks to the project regardless of how complex the site actually is. This is the part of planning that is hardest to template, because it depends on the client&#8217;s internal process more than the agency&#8217;s.<\/p>\n\n\n\n<h2 id=\"conclusion\" class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The website planning process is not a delay before the real work starts. It is the real work, done in the order that prevents the most expensive mistakes. A goal defined in one sentence. A sitemap built around what visitors are trying to do. A content plan with named owners. A technical checklist covered before design begins. That sequence is what keeps a project on its original timeline instead of a revised one, and it is the difference clients notice most once the site is actually live.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your business is weighing a new website or a redesign, the place to start is not a mood board. It is a plain conversation about what the site needs to do and for whom. <a href=\"https:\/\/push.digital\/#contact\">Talk to our brand team at Push Digital<\/a> about what that planning conversation would cover for your business specifically.<\/p>\n\n\n\n<h2 id=\"frequently-asked-questions\" class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1791535338723\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is the website planning process?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>The website planning process is the stage before design where goals, sitemap, content, and technical needs get defined. It produces documents the design and build stages are built against, rather than decided mid-project.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791535374326\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">How long does website planning take before design starts?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Most projects need two to six weeks for planning before design begins. The main factor is how fast stakeholders review and approve each stage, not the site&#8217;s page count.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791535381210\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is included in a website brief or discovery phase?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>A website brief covers the site&#8217;s goal, target audience, competitor review, and a first pass at the pages needed. It gets revised as planning uncovers details the initial conversation missed.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791535390938\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What&#8217;s the difference between a sitemap and information architecture?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>A sitemap lists the pages a site will have. Information architecture defines how those pages connect and how a visitor moves between them to complete a task.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791535403219\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Why is website planning important before development?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Planning catches structural and content gaps while they are cheap to fix. Design and development built on an unfinished plan usually get partially rebuilt once the missing details surface.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791535413657\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What questions should a business answer before building a website?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>At minimum: the site&#8217;s single primary goal, its main audience, which pages are essential versus optional, and who owns writing the content for each page.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Most website conversations start the wrong way. A business owner calls an agency, mentions a few pages they want, and asks how&#8230;<\/p>\n","protected":false},"author":1,"featured_media":471,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-470","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development"],"_links":{"self":[{"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/posts\/470","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/comments?post=470"}],"version-history":[{"count":1,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/posts\/470\/revisions"}],"predecessor-version":[{"id":476,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/posts\/470\/revisions\/476"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/media\/471"}],"wp:attachment":[{"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/media?parent=470"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/categories?post=470"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/push.digital\/blog\/wp-json\/wp\/v2\/tags?post=470"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}