If your WordPress site has more than a handful of services, locations, case studies or team members, the most reliable way to keep it consistent is to stop building each one as a free-form page and instead store them as structured content: a custom post type for each kind of thing, with named fields for the parts that change (price band, duration, area served, FAQs) and a single template that lays them out. Done well, it makes new pages faster to publish, keeps design and schema consistent, and lets you change a layout once instead of forty times. Done badly, it produces forty near-identical thin pages that Google ignores. This guide explains when structured content is worth it for a web development company's clients in Pune and across India, how to build it in WordPress, and where it goes wrong.
It is written for owners and marketers of service businesses (clinics, coaching institutes, interior designers, equipment suppliers, accountants, event companies) who are about to commission a WordPress site or who inherited one built entirely with a page builder, and for developers who want a sanity check on their approach. It assumes no coding, but it does name the WordPress features involved so you can ask a developer for them by name.
The problem with building every page by hand
Most small-business WordPress sites begin the same way. Someone builds a "Services" page, then a page per service, copying the previous one each time and editing the text. It works for five pages. By twenty, three things have usually gone wrong.
Inconsistency. The "Physiotherapy" page has a price table, the "Dental" page has none, and the "Skin" page puts the call button in a different place. Visitors cannot learn the pattern, and you cannot tell whether a difference is deliberate.
Fragile design changes. When you want to move the WhatsApp button or add a booking note, you edit every page. Page builders offer "global" blocks, but copied sections are still copies, and a few always get missed.
Thin or duplicated content. When a person has to fill a blank canvas twenty times, shortcuts follow: the same three paragraphs with a different noun. Google's guidance on scaled or low-value content is clear that pages made mainly to occupy a keyword rather than help a reader are a risk, and a site full of near-duplicate pages invites exactly that reading. Our guide to service-area and location pages without doorway content covers that trap in detail.
Hard-to-reuse data. Your opening hours, price bands and service descriptions live inside paragraphs. You cannot show "three related services" at the bottom of a page, build a filterable list, or generate structured data from them, because the information is not stored as information.
Structured content addresses the last point most directly and, as a side effect, the other three.
What "structured content" means in WordPress
WordPress ships with two built-in content types, posts and pages. A custom post type is a third kind that you define: "Service", "Case study", "Team member", "Location", "Course", "Equipment model". Each gets its own admin menu, its own list screen, its own URL pattern and its own template. The official developer documentation describes how custom post types are registered, and it is worth a skim if you want to understand what your developer is doing: see the WordPress Developer Resources page on custom post types.
A custom field stores one named piece of information attached to a post: "starting price", "typical duration", "areas served", "registration number". Fields are what turn a blank page into a form. A taxonomy is a way to group items: "Service category", "City", "Industry". WordPress has built-in categories and tags and lets you register your own.
Put together, a service listing becomes:
- Post type: Service
- Taxonomy: Service category (Dental, Skin, Physio)
- Fields: short summary, who it is for, what is included, what is not included, typical duration, starting price or price band, preparation, an image, three FAQs, related services
- Template: one layout that shows these in a fixed, designed order
The person adding the twenty-first service fills a form and presses publish. The page that results looks like the other twenty.
When you should not use custom post types
Structured content is not always the right answer, and an honest agency will say so.
- Fewer than about six similar items, with no growth planned. Hand-built pages may be quicker and more flexible. The overhead of a post type pays back only through repetition.
- Every page is genuinely different. A campaign landing page, a long story or a one-off event page needs freedom. Keep those as pages.
- You have no one to maintain it. A custom post type is code or a plugin configuration. Someone has to own it through WordPress updates.
A useful rule: if you can describe the item as "the same questions answered about a different thing", it belongs in a post type. If every item needs a different argument, it is a page.
Step 1: Define the content model on paper
Before anyone opens WordPress, list the kinds of thing your site is about, and for each, the questions a customer asks. This is the most valuable hour of the project.
Take an example. Suppose a Pune interior design studio wants pages for each type of project it takes on. The studio lists:
- Service: full-home interiors, modular kitchens, wardrobe fit-outs, office fit-outs
- Project (case study): a completed job with photographs, location (area, not street address), size, duration, what was done
- Material or style guide: optional editorial content
For Service the customer questions are: What is it? Who is it for? What is included? What is not included? How long does it take? What does it cost, roughly? What do I need to decide before we start? Has the studio done this before (link to projects)? Those questions become the fields. Notice the "what is not included" question: it is the one most hand-built pages skip, and it is the one that prevents disputes later.
Illustrative only: if you offer packages, store the price as a "starting from" figure and a note on what moves it, rather than a single number you must defend forever. Do not publish a price band you cannot honour; see our article on pricing pages and quote forms for service websites for how to present ranges honestly.
Write the model as a table: item type, fields, who edits it, how many items you expect in a year. Two minutes with that table will expose most of the mistakes.
Step 2: Register the post type and fields
There are three practical ways to build this.
Option A: A plugin-driven setup
Plugins such as Advanced Custom Fields (ACF), Meta Box, Pods or Toolset let you register post types and fields from a screen in the admin. This is how many agencies work because it is fast and understandable by the next developer. The trade-offs: you depend on a plugin being maintained, and the configuration lives in the database unless you export it to files. Use the plugin's option to save field definitions as files in the theme or plugin and keep them in version control, so a rebuild does not lose them.
Option B: Code in a small custom plugin
A developer registers the post types, taxonomies and fields in a small plugin of their own using the core functions register_post_type() and register_taxonomy() and the Block Editor's meta features. This has no third-party dependency for the structure and is easiest to test and review. It costs more developer time up front and is harder for a non-technical team to adjust.
Option C: Block-theme patterns and synced patterns
Modern WordPress block themes support custom templates and reusable patterns. For modest needs, a template for the "Service" post type built in the Site Editor, with fields stored through block bindings or a lightweight plugin, may be enough. This is changing quickly, so ask your developer which approach the current WordPress release supports well rather than assuming.
Where the code lives matters more than which option you pick. A rule we recommend: structure (post types, taxonomies, fields) goes in a plugin, not the theme. If the structure is in the theme and you change themes in two years, your services vanish from the admin. Presentation (templates, styles) goes in the theme.
Step 3: Design the template once, then test it with awkward content
Create one single-item template and one archive template for each post type. Then deliberately break them:
- A service with a 90-character title and one with a 12-character title
- A service with no price, no image, and no FAQs
- A service with eight FAQs and four images
- Text pasted from Word with odd formatting
If the layout holds, you are in good shape. If it collapses, you have found the fields that need defaults and fallbacks, such as hiding an empty "price" row instead of showing a blank label.
Treat required versus optional fields as a design decision. Make "summary" and "what is included" required so no page goes live without them, and make "price" optional so you are not forced to publish a number you do not have.
Check the template on a phone first. As with any service page, the first screen should say what the service is and offer one obvious action; our guide to service page design that produces enquiries explains what that looks like.
Step 4: Let the structure drive your metadata and schema
Here is the second big benefit. Because the information is stored in fields, you can generate consistent markup from it.
- Title and meta description patterns. A rule such as "[Service name] in Pune: what is included, timeline and cost" gives a sensible default that the editor can override. Defaults should never be the final word: Google treats pages with identical or boilerplate titles as low quality, and the plugin should flag any page whose title was left on the default.
- Breadcrumbs that reflect the taxonomy: Home > Services > Dental > Root canal. See internal linking and breadcrumbs for site architecture.
- Structured data. A Service or Product-like description, plus Organization or LocalBusiness details, can be output from the same fields. Only mark up what is visible on the page, which Google's structured data guidelines require. Do not output a FAQPage block unless the FAQs are actually shown to visitors. Our article on structured data and JSON-LD for local businesses covers what to include. Note that Google has restricted FAQ rich results to a small set of authoritative sites, so do not expect visible FAQ snippets from FAQ markup; the FAQs are still useful to readers.
- Related items. A "related services" field, or a rule that shows items from the same category, builds internal links automatically and keeps a visitor moving.
Always test generated markup with Google's Rich Results Test and the Schema Markup Validator on at least one example of each template before launch.
Step 5: Plan the URLs and redirects
A post type gets a URL pattern, such as /services/root-canal/ or /projects/koregaon-park-3bhk/. Decide it early, because changing it later requires redirects for every item.
- Keep slugs short, readable and permanent. Do not include dates in a URL unless the content is date-bound.
- Decide whether the archive (
/services/) is a real, useful page with an introduction or an automatic list. Give it a proper introduction written by a human; an unmodified auto-list is a weak page. - If you are replacing an existing site, build a redirect map from old URLs to new ones before switching. Our guide to content inventory, sitemap and redirect map before a redesign shows the sheet to use.
- Make sure your XML sitemap includes the new post types and excludes anything that should not be indexed, such as internal draft types.
Step 6: Give editors a safe, simple admin
The point of structured content is that staff can maintain it. Spend an hour on the editing experience.
- Label fields in plain language. "What is included (list, one per line)" beats "service_inclusions".
- Add help text with a real example under any field that people misuse.
- Limit roles. An editor who updates prices does not need to see plugin settings. Use WordPress roles, and keep administrator access to the few people who need it.
- Set a review habit. Fields like price and duration go stale. Add a "last reviewed" date field and show it, or at least a quarterly reminder, so old numbers do not mislead customers.
- Document it on one page. A half-page guide titled "How to add a service" saves a support call every time a new person joins.
Step 7: Performance and maintenance
Structured content can be fast or slow depending on how it is queried and presented.
- Avoid loading every field for every list. An archive that shows twenty services needs the title, summary and image, not all the long fields.
- Cache the output. Page caching works the same way for custom post types as for pages. Test that editing a service clears the cache for that page and its archive.
- Image sizes. Define the image sizes the template needs, so editors do not upload a 6 MB photograph into a thumbnail slot. See image optimisation with AVIF and WebP.
- Plugin hygiene. Every plugin you add to manage fields is something to keep updated. Review them regularly; see our WordPress plugin audit for abandoned plugins.
- Back up before structural changes. Renaming a field or changing a post type slug can orphan data. Take a backup, and test on a staging copy first.
A worked example: a Pune training institute
To make this concrete, here is an illustrative scenario. The numbers are for planning and are not results from a specific client.
A training institute offers around thirty courses. Today each is a hand-built page. The owner wants the site to produce enquiries for each course and to be easy for staff to update when batch dates change.
The content model. Post type "Course". Taxonomy "Course category" (accounting, design, languages) and "Mode" (classroom, online). Fields: one-line summary, who it is for, prerequisites, syllabus (a repeater of modules), duration, batch start dates (repeater), fee (optional, with a note on instalments), certificate details, three FAQs, and a link to a related course.
The template. First screen: course name, summary, "Next batch: [date]", and one primary button, "Ask on WhatsApp", whose message is pre-filled with the course name. Then syllabus, who it is for, fees, FAQs. Our guide to click-to-call and WhatsApp buttons on mobile service sites covers the button details.
What the structure buys them. Staff update batch dates in a field, and the date appears on the course page, in the archive card and in the Google Business Profile post they copy it into. A new course takes about as long as filling a form. Because "prerequisites" and "who it is for" are required fields, no course page is missing the information students ask about.
What it does not buy them. It does not guarantee rankings. Each course page still needs unique, useful text, and thirty pages with the same boilerplate in the free-text fields will perform no better than thirty hand-built ones. The structure makes consistency cheap; quality still comes from the people filling it.
Common mistakes
- Using a post type to publish thin pages at scale. If you generate two hundred pages by combining "service" and "area" with almost no unique content, you are building doorway pages. Do not.
- Putting structure in the theme. Changing the theme later deletes your content model.
- Too many fields. Thirty fields per item means nobody fills them in. Start with the eight questions customers actually ask.
- Fields nobody reads. If a field does not appear on the page or feed anything, remove it.
- No fallback for empty fields. Blank headings and empty boxes look broken and hurt trust.
- Ignoring the archive page. Archives and category pages are often your strongest entry points. Give them real introductions.
- Forgetting redirects when you change URL structure.
Cost and timeline
We cannot quote a single honest number for "adding custom post types", because the cost depends on how many types and fields, how bespoke the design is, and whether existing content must be migrated. As a planning guide, treat structured content as a design-and-content exercise rather than a plugin purchase: the content model, template design and migration of existing pages are where the time goes. If an agency quotes you a flat low figure for "custom post types" with no mention of the content model, redirect plan and editor training, ask what is being left out. For a broader view of what drives website cost, see our guide to website design cost. TODO: add a sourced rupee range once confirmed against current Govindani project quotes.
What to ask a developer in Pune
- Which post types and fields will you create, and can I see the content model before you build?
- Is the structure in a plugin or the theme?
- Are field definitions saved as files and kept in version control?
- How will URLs, redirects and the XML sitemap be handled?
- What will the editor see, and who gets which role?
- How will you test the template with empty and extreme content?
- Who maintains it after launch, and what happens at WordPress updates?
A developer who answers these in concrete terms has built this before.
Work with the Govindani team
We build WordPress and custom-coded websites for service businesses, e-commerce stores and non-profits from our Pune office, and we plan the content model before touching the design. If you want to turn a pile of hand-built pages into a maintainable site, see our website creation services or our SEO services for the search side, then contact us or call 092019 58274.
Frequently asked questions
What is a custom post type in WordPress?
A custom post type is a content type you define yourself, such as Service, Course or Project, alongside the built-in posts and pages. It gets its own admin menu, URLs and templates, which keeps repeated kinds of content consistent and easy to manage.
Do I need a plugin like ACF for custom post types?
No. Post types and fields can be registered with WordPress core functions or a small custom plugin. Plugins such as ACF, Meta Box or Pods make the setup faster and friendlier for non-developers, at the cost of another dependency to keep updated.
Do custom post types help SEO?
Indirectly. They make consistent titles, breadcrumbs, internal links and structured data easy, but they do not rank pages by themselves. Each page still needs unique, genuinely useful content, and publishing many near-identical pages can harm a site.
Should structure live in the theme or a plugin?
In a plugin. If post types and fields live in the theme, switching themes later removes them from the admin. Keep presentation in the theme and structure in a plugin.
How many fields should a service post type have?
Start with the questions customers actually ask, usually six to ten, such as what is included, who it is for, duration and starting price. Add more only when a field will appear on the page or feed something useful.
Sources:
- WordPress Developer Resources: Registering custom post types
- Google Search Central: Spam policies for Google web search (scaled content abuse)
- Google Search Central: General structured data guidelines
- Google Search Central: FAQ structured data
About the author: written by the Govindani Infotech web design and development team in Pune.