Internal Reference · Not Indexed
Blog Publishing
Rules & Standards
The single source of truth for creating and publishing any blog post on cinemotive.com.au. Follow this before publishing. Share with anyone who publishes content on the site.
Categories
Every post must have exactly one category. Choose from the five active categories below. Do not create new categories without a clear, ongoing content need.
Individual wedding story pages. Each post covers one couple's wedding day — ceremony, venue, cultural traditions, photos and/or film.
Use forAny published wedding story. This is the category the filter grid on the Real Weddings page pulls from automatically.
Never use forChristenings, editorial content, planning guides, or any post that is not a specific couple's wedding.
Baptism and christening portfolio pages. Same structure as Real Weddings but for christening coverage — ceremony, venue, family, photos and/or film.
Use forAny published christening story. Keep separate from Real Weddings so each can have its own filter grid in future.
Never use forWeddings or any non-christening content.
All editorial and educational content. Planning guides, timing articles, atmosphere and flow pieces, venue guides, advice posts.
Use forAny post that helps couples plan, think through, or understand their wedding — regardless of whether it features a specific couple.
Never use forWedding story pages. If there's a couple featured, it's Real Weddings, not Wedding Planning.
Portfolio pages for Celebration of Life events. Same structure as Real Weddings but for this specific service.
Use forAny published Celebration of Life story page.
Never use forWeddings, christenings, or editorial content.
Studio and team content. Team updates, process pieces, studio news, industry content. Optional — only publish if there's a clear ongoing use for this content type.
Use forStudio-side content that doesn't fit any other category.
Never use forClient portfolio content of any kind.
Tag System
Tags serve two purposes: powering the filter system on the Real Weddings page, and supporting SEO. The filter system reads prefixed tags only — plain tags are used for SEO and are ignored by the filter.
Assign the primary cultural or religious tradition visible on the day. Tag by what happened on camera — not family heritage alone.
Mixed culture weddings get both Ct- tags plus Ct-Mixed Culture so they appear in all three relevant filters.
Tag the reception venue — where the evening was held. One tag per wedding unless there were two distinct reception spaces.
Tag the church or ceremony location. Use the full common name — the same name a couple would type into Google when searching for it.
Every Real Wedding post should have a Ch- tag. It's a genuine search intent — couples look for photographers who've shot at their church.
Tag the broad geographic area of the photoshoot. This becomes the primary chip in the photoshoot filter. Always add this alongside any Pl- specific tags.
One per geographic region. Always pair with Pl- tags for the specific spots used.
Tag every specific location used during the photoshoot. Multiple Pl- tags per wedding is correct — most shoots hit 2–4 spots. These appear as sub-chips under the broad Ps- area.
Use the well-known public name — what a couple would search for, not an internal shorthand.
Every post gets exactly one Ac- tag. This tells the system how to render the content — fully open or as a locked teaser card with a request access trigger.
Ac-Public — fully visible to everyone. Ac-Request — renders as a locked teaser in the filter grid and further reading strip. Couple submits email → you approve → they receive access. Every post must have one of these two tags.
Tag Rules
| Rule | Correct | Incorrect |
|---|---|---|
| Exact spelling. The filter reads tags as strings — one typo and a post won't appear in that filter. | Ct-Greek Orthodox | ct-greek orthodox / Ct-Greek Orthdox |
| Tag by what happened on the day — not by cultural background alone. | What was visible on camera | What the family background is |
| Mixed cultures: both Ct- tags plus Ct-Mixed Culture. | Ct-Greek Orthodox + Ct-Anglo + Ct-Mixed Culture | Just one tag when two cultures were present |
| Vn- = reception venue only. Never use Vn- for a church or ceremony space. | Vn-Ivy Ballroom | Vn-St Mary's Cathedral |
| Ch- = ceremony venue. Use the full common name Google would recognise. | Ch-St Mary's Cathedral | Ch-St Marys / Ch-the cathedral |
| Ps- = broad photoshoot area. Always pair with Pl- specific location tags. | Ps-Sydney CBD + Pl-State Library + Pl-Martin Place | Ps-State Library (too specific for a broad area tag) |
| Pl- = specific photoshoot spots. Multiple Pl- tags per wedding is correct and encouraged. | Pl-State Library + Pl-Hyde Park + Pl-Barangaroo | Only tagging one spot when several were used |
| Ac- = access level. Every post gets exactly one — either Ac-Public or Ac-Request. Never both, never neither. | Ac-Public or Ac-Request (one only) | Missing the Ac- tag entirely |
| Every Real Wedding post must have Ct-, Vn-, Ch-, and Ac- tags before publishing. Ps- and Pl- required if a photoshoot location was used. | All required tags confirmed before Publish | Publishing and adding tags later |
Publishing Checklist
Run through every item before hitting Publish. All items must be complete. No exceptions.
- 01 Category assigned. One category only, from the five active categories in Section 1. Real Weddings for couple stories, Christenings for baptism stories, Wedding Planning for editorial.
-
02
Slug confirmed. See Section 4 for format rules. All lowercase, hyphens only, no dates. Example:
adam-alexandra-st-marys-cathedral-ivy-ballroom -
03
SEO title tag. Under 60 characters. Format for weddings:
[Names] Wedding at [Venue] | CineMotive Sydney - 04 Meta description. 140–155 characters. Lead with culture and venue. No forbidden words. No clichés.
-
05
Focus keyword set. Format:
[culture] wedding [venue] sydney— e.g.greek orthodox wedding linseed house sydney - 06 Ct- tag(s) applied. At least one culture tag. Required on all Real Weddings posts. Mixed culture = both Ct- tags + Ct-Mixed Culture.
- 07 Vn- tag applied. Reception venue. One per wedding. Required on all Real Weddings posts.
- 07b Ch- tag applied. Ceremony venue — church, chapel, or ceremony space. Use the full common name. Required on all Real Weddings posts.
-
07c
Ps- tag applied. Broad photoshoot area (e.g.
Ps-Sydney CBD). One per geographic region. Always pair with Pl- specific tags. -
07d
Pl- tag(s) applied. Every specific photoshoot location used (e.g.
Pl-State Library,Pl-Martin Place). Multiple tags per wedding is correct. -
07e
Ac- tag applied. Exactly one — either
Ac-PublicorAc-Request. Required on every post. Controls whether content renders open or as a locked teaser. - 08 Featured image set. Horizontal hero crop. Minimum 1200 × 630px. This is used for the grid tile on the Real Weddings page and as the Open Graph image when shared.
-
09
Story wrapped in
#cm-storycontainer. Build the entire post body — hero image, text, gallery, film — inside one outer Elementor Section or Container. Select it → Advanced tab → CSS ID field → entercm-story(exactly, lowercase, no variations). Every post uses the same ID. This makes the post ready for the in-page overlay viewer planned for the Real Weddings grid; keep the whole story self-contained inside it and don't rely on anything sitting outside this container. - 10 Couple name order correct. Follow cultural convention — groom first for Lebanese, Coptic, and Arabic couples. Confirm before writing the H1.
- 11 No forbidden words. Search the post body before publishing. See Section 5 for the full list.
- 12 At least one internal link. Link to Photography, Film, Investment, or Contact page within the post body.
- 13 Coverage type noted. Somewhere on the page — even subtly — indicate Photo only / Film only / Photo & Film.
Slug Format
The URL slug is permanent once a post is indexed. Get it right before publishing — changing it later requires a redirect.
firstname-lastname-ceremony-venue-or-reception-venue
adam-alexandra-st-marys-cathedral-ivy-ballroom
firstname-lastname-christening-venue-name
descriptive-title-of-the-post-topic
| Rule | Yes | No |
|---|---|---|
| All lowercase | adam-alexandra-ivy-ballroom | Adam-Alexandra-Ivy-Ballroom |
| Hyphens only — no underscores, no spaces | greek-orthodox-wedding-linseed-house | greek_orthodox_wedding_linseed house |
| No dates in the slug | adam-alexandra-ivy-ballroom | adam-alexandra-ivy-ballroom-2026 |
| No "wedding" in slug for couple pages — it's implied | adam-alexandra-ivy-ballroom | adam-alexandra-wedding-ivy-ballroom |
| Keep it under 60 characters where possible | nickolas-anastasia-greek-linseed-house | nickolas-and-anastasia-greek-orthodox-wedding-at-linseed-house |
SEO Rules
These apply to every post. AIOSEO handles the fields — fill them every time before publishing.
-
T
SEO title tag: Under 60 characters. For weddings:
[Names] Wedding — [Venue] | CineMotive Sydney. For editorial: natural title + brand. Never copy the H1 verbatim. - D Meta description: 140–155 characters. For weddings: lead with culture + venue, include Sydney. For editorial: lead with the core insight or topic. No clichés. No forbidden words.
-
K
Focus keyword: One per post. For weddings:
[culture] wedding [venue] sydney. For editorial: the specific search term the post targets. - OG Open Graph image: Set the featured image — AIOSEO uses this automatically for OG. Minimum 1200 × 630px, horizontal, high quality hero shot.
- IL Internal links: At least one link to a core CineMotive page (Photo, Film, Investment, Contact) within the body. Helps with site architecture and passing link equity.
Copy Rules
CineMotive copy is couple-centric, direct, and free of wedding industry clichés. These rules apply to all published content.
| Principle | Do this | Not this |
|---|---|---|
| Write about the couple — not about CineMotive's work | The morning began with Croatian traditions at the family home in Strathfield. | We captured the beautiful Croatian traditions with our signature style. |
| Name what happened — not how it felt in generic terms | The zaffe arrived at 11am. The room hadn't settled by the time it left. | The magical atmosphere was unforgettable for everyone in the room. |
| Cultural specificity — name the traditions, the church, the customs | St Gerasimos Church, Zembekiko, the crowning, plate smashing at Alpha. | A beautiful ceremony full of cultural traditions and heartfelt moments. |
| Tone: warm, direct, editorial — not sales-y or gushing | Structure gave the day shape. Movement gave it life. | It was an absolutely stunning wedding we were so privileged to capture! |
| Name order: follow cultural convention for couple names | Salim & Nicola (groom first — Lebanese convention) | Nicola & Salim |
API Reference
For developers building or maintaining the filter grid on the Real Weddings page. These are the live WordPress REST API endpoints used by the filter system.
Fetch all Real Weddings posts (category ID 79) with embedded tag data:
https://cinemotive.com.au/wp-json/wp/v2/posts?categories=79&per_page=100&_embed
Filter logic — how the grid reads tags:
Tags starting with "Ct-" → Culture filter chips — primary (always visible)
Tags starting with "Vn-" → Reception Venue filter chips — primary (always visible)
Tags starting with "Ch-" → Ceremony Venue filter chips — secondary (collapsed)
Tags starting with "Ps-" → Photoshoot Area chips — secondary (broad, collapsed)
Tags starting with "Pl-" → Photoshoot Location chips — secondary (specific, sub-chips under Ps-)
Tags starting with "Ac-" → Access control — not a filter chip; controls open vs locked rendering
All other tags → ignored by filter, used for SEO only
All site categories (to find IDs for new categories):
https://cinemotive.com.au/wp-json/wp/v2/categories?per_page=100
All site tags (to audit existing Ct- and Vn- tags):
https://cinemotive.com.au/wp-json/wp/v2/tags?per_page=100&search=Ct-
https://cinemotive.com.au/wp-json/wp/v2/tags?per_page=100&search=Vn-
Legacy Categories
These categories exist on the site from previous use. Do not assign any new posts to them. Existing posts in these categories can stay — do not delete the categories as this may break existing posts.
