<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Christopher Nowlan on Medium]]></title>
        <description><![CDATA[Stories by Christopher Nowlan on Medium]]></description>
        <link>https://medium.com/@hello_82362?source=rss-9f70aa81d44c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Q2fzIasBqnQdEsRW</url>
            <title>Stories by Christopher Nowlan on Medium</title>
            <link>https://medium.com/@hello_82362?source=rss-9f70aa81d44c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:33:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hello_82362/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[We found 6 broken links in our own blog: Catching route changes in CI]]></title>
            <link>https://medium.com/@hello_82362/we-found-6-broken-links-in-our-own-blog-catching-route-changes-in-ci-d8823468b6b0?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8823468b6b0</guid>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 11:41:01 GMT</pubDate>
            <atom:updated>2026-11-11T11:41:01.579Z</atom:updated>
            <content:encoded><![CDATA[<p>We renamed a few blog slugs during a content restructure and missed six internal links pointing to the old URLs. No build errors. No CMS warnings. Just quiet 404s sitting there, leaking the link equity those pages had earned.</p><h3>The invisible reference problem</h3><p>Internal links in a CMS-driven site are different from internal links in a traditional codebase. In code, a linter or IDE can flag a broken import. In a CMS, most internal links live inside rich text fields, serialised data in the database. Nobody sees them. Nothing validates them.</p><p>Payload CMS supports document-level references, linking to a document by ID rather than by URL. When the document’s slug changes, the link stays valid. We use this wherever possible. But not every link can be a document reference. Some are hardcoded paths in rich text or CTA blocks. Those are the ones that break silently.</p><h3>What we built</h3><p>We added a link checker to our CI pipeline. On every push, the build generates the full sitemap, then a script crawls every internal link on every page and checks it against that sitemap. If a link points to a URL that isn’t in the sitemap, the build fails.</p><p>Not a warning. A failure. Warnings get ignored. Failed builds get fixed.</p><p>The check covers rich text, navigation, CTA blocks, footer links, and hardcoded component references. The developer sees which page contains the broken link, which URL it targets, and can either update the link or add a redirect in the CMS.</p><h3>The broader pattern</h3><p>Broken links are one example of content integrity checks that a CMS doesn’t handle natively. Missing alt text. Orphaned pages. Redirect chains. Meta descriptions over character limits. Each of these can be validated programmatically, the question is where.</p><p>We run both: CMS-level validation for immediate editor feedback (required fields, image dimensions) and CI-level validation for things that only surface in the full rendered build (broken links, redirect chains, sitemap gaps).</p><h3>The takeaway</h3><p>If your site is CMS-driven, rich text links are your blind spot. Document references solve part of it. A CI check that crawls every internal link solves the rest.</p><p>Six broken links across 50 posts. Found by accident during an audit. Now found automatically on every push.</p><p>We build CMS-driven websites on Payload CMS and Next.js — with CI pipelines that catch content integrity issues before they go live. If you’re scaling a content-heavy site and want fewer silent failures, <a href="https://meetings.hubspot.com/chris-nowlan/little-dash-discovery-call">book a discovery call</a> or visit <a href="https://littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8823468b6b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enquiry forms that land in the CMS and the CRM]]></title>
            <link>https://medium.com/@hello_82362/enquiry-forms-that-land-in-the-cms-and-the-crm-938b0327d174?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/938b0327d174</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[forms]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 04:16:01 GMT</pubDate>
            <atom:updated>2026-11-03T04:16:01.724Z</atom:updated>
            <content:encoded><![CDATA[<p>Most contact forms on marketing sites are doing one job, sending an email. Maybe two, if there’s a CAPTCHA. The submission arrives in a shared inbox, someone forwards it to the sales team, and the CRM gets updated manually. If it gets updated at all.</p><p>The form “works.” But every seam between systems is a place where leads leak.</p><h3>Three jobs, one server action</h3><p>We handle spam filtering, CMS storage, and CRM sync in a single Next.js server action. The form submits to the server, no client-side API keys, no exposed endpoints.</p><p><strong>Step one: reCAPTCHA v3 verification.</strong> Invisible to the visitor, no checkboxes, no image puzzles. Google scores the visitor’s behaviour. We verify the token server-side and reject submissions below a confidence threshold.</p><p><strong>Step two: Payload CMS submission.</strong> Every enquiry is stored as structured content, name, email, message, source page, timestamp. This is the audit trail. The team can search, filter, and export submissions from the CMS admin.</p><p><strong>Step three: HubSpot form submission.</strong> The same data is sent to HubSpot’s API with page context. The enquiry lands in the CRM pipeline. The sales team picks it up in HubSpot’s workflow, not in a forwarded email.</p><p>If any step fails, the others still complete. A HubSpot timeout doesn’t prevent the Payload submission from being stored.</p><h3>Why server-side matters</h3><p>Client-side form handling exposes secrets. A reCAPTCHA key in browser JavaScript can be extracted. A HubSpot API key in a client-side fetch call is visible in the network tab. Server actions keep credentials on the server where they belong.</p><p>Server-side validation is also the actual security boundary. Client-side validation tells visitors their email is malformed. Server-side validation ensures the data that reaches your CMS and CRM meets the real requirements, regardless of what the browser sent.</p><h3>The spam tradeoff</h3><p>reCAPTCHA v3 scores visitors from 0 (likely bot) to 1 (likely human). The threshold is a tradeoff, too strict and legitimate enquiries get blocked, too lenient and spam gets through.</p><p>There’s no universally correct number. We start with a reasonable default and adjust based on what actually arrives. The submissions stored in Payload make this easy to audit. The team can see what was accepted, spot patterns in spam that’s getting through, and adjust the threshold accordingly.</p><h3>Two systems, two purposes</h3><p>Payload is the source of truth, every submission stored, searchable, exportable. HubSpot is the action layer, pipelines, workflows, follow-up tracking. The development team references Payload. The sales team works in HubSpot. Neither needs to switch tools.</p><p>The form looks like a simple contact page. Underneath, it’s a pipeline that filters, stores, and routes, without the visitor noticing any of it.</p><p>Little Dash builds enquiry pipelines that filter spam, store submissions in the CMS, and sync to your CRM. If your current forms are leaking leads between systems, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=938b0327d174" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redirects that editors own (and search engines respect)]]></title>
            <link>https://medium.com/@hello_82362/redirects-that-editors-own-and-search-engines-respect-c7df68ce541a?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7df68ce541a</guid>
            <category><![CDATA[redirect]]></category>
            <category><![CDATA[seo-redirects]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 04:11:01 GMT</pubDate>
            <atom:updated>2026-10-27T04:11:01.690Z</atom:updated>
            <content:encoded><![CDATA[<p>Every website accumulates URL debt. Services get renamed. Blog posts get recategorised. Entire sites get rebuilt on new platforms with different information architectures. Without redirects, every old URL becomes a dead end, for visitors and for the search equity those pages earned.</p><p>Most teams handle redirects one of two ways: developers add them to a config file, or someone maintains a spreadsheet that gets translated into server rules every few weeks. Both work until they don’t.</p><p>The underlying issue is ownership. Redirects are a content concern dressed up as a technical one. The people who know which URLs changed are editors and project managers. The people who can implement redirects are developers. That gap creates delays.</p><h3>Redirects as CMS content</h3><p>We store redirects in Payload CMS as first-class content entries. An editor creates a redirect with a source path and a destination, either a URL or a reference to a CMS document. On the Next.js side, a utility fetches all active redirects, caches them with a dedicated cache tag, and checks incoming requests before returning a 404.</p><p>The cache tag matters. Redirects change infrequently, so there’s no reason to query the database on every request. The full set is cached until an editor creates, updates, or deletes a redirect. At that point, a collection hook busts the cache, and the next request picks up the fresh set.</p><h3>What this gives editors</h3><p>Once redirects live in the CMS, editors can handle URL renames in the same session as the content change, no waiting for a deployment. Migration cleanup becomes a bulk import task. Destinations can reference CMS documents rather than hardcoded paths, so if the destination page’s slug changes later, the redirect still resolves correctly.</p><p>And the redirect collection is searchable. The team can audit active redirects, spot chains, and clean up entries that are no longer needed. All without a developer ticket.</p><h3>Where config-level redirects still belong</h3><p>Not every redirect is a content decision. Domain-level redirects (www normalisation, HTTPS enforcement) belong in hosting configuration. Trailing-slash rules belong in the framework. These are infrastructure concerns that should deploy with the codebase.</p><p>The split is clean: if an editor would reasonably need to create or change it, it goes in the CMS. If it’s a platform rule that applies regardless of content, it stays in config.</p><h3>Why speed matters for SEO</h3><p>A 301 redirect tells Google the old URL has permanently moved, and ranking signals, backlinks, page authority, crawl history, should transfer to the new destination. A missing redirect means those signals are lost.</p><p>The longer a 404 persists after a URL change, the more likely Google is to drop the page from the index. CMS-managed redirects close that gap. The redirect is created alongside the URL change, live within seconds, and cached for performance.</p><p>Little Dash builds redirect management into every platform migration so link equity transfers cleanly and editors stay in control. If you’re planning a site rebuild or restructure, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7df68ce541a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Responsive design isn’t a feature, it’s a ranking signal]]></title>
            <link>https://medium.com/@hello_82362/responsive-design-isnt-a-feature-it-s-a-ranking-signal-6a74ee1f42f1?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a74ee1f42f1</guid>
            <category><![CDATA[google-ranking]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[mobile-first]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Tue, 20 Oct 2026 09:41:01 GMT</pubDate>
            <atom:updated>2026-10-20T09:41:01.949Z</atom:updated>
            <content:encoded><![CDATA[<p>Most businesses assume their site “works on mobile.” Open it on a phone, everything fits the screen, job done.</p><p>But Google’s mobile-first indexing changed the stakes. The mobile version of your site is what Google indexes, evaluates, and ranks. Not the desktop version. Not both. Mobile.</p><h3>The gap between responsive and mobile-optimised</h3><p>A responsive site adjusts its layout to different screen sizes. A mobile-optimised site is designed to work well on small screens with touch input and variable network conditions. These are different things.</p><p>A site can be technically responsive, every element fits the screen — while still delivering a poor mobile experience. Tiny tap targets. Text that requires pinching. Desktop-resolution images loading on mobile data. Navigation designed for mouse precision rather than thumb reach.</p><p>Google evaluates both the layout adaptation and the quality of the mobile experience. Layout is table stakes. Experience is where rankings are won or lost.</p><h3>How responsive design affects SEO signals</h3><p>It’s not one ranking factor. Responsive design affects multiple signals simultaneously.</p><p><strong>Core Web Vitals on mobile.</strong> Google measures CWV on mobile devices specifically. LCP is affected by serving oversized images. CLS is affected by elements that resize unpredictably across breakpoints. INP is affected by JavaScript blocking touch interactions. A site passing CWV on desktop can fail on mobile, and mobile is what counts.</p><p><strong>Content parity.</strong> Content hidden on mobile via display: none may be deprioritised or ignored by Google entirely. Internal links hidden behind hamburger menus don&#39;t pass PageRank the same way. The mobile content is the content Google indexes.</p><p><strong>Page speed on mobile networks.</strong> Mobile devices operate on slower, higher-latency connections. Images not sized for the viewport, render-blocking scripts, and heavy bundles have a disproportionate impact. A 1920px JPEG loading on a 375px phone over 4G is wasted bandwidth and a slower LCP.</p><h3>Component-level, not page-level</h3><p>Most teams treat responsive design as a page concern, “make the homepage work on mobile.” We treat it as a component concern. Every block in our CMS library is responsive independently. When a new page is assembled from existing blocks, it’s responsive by default.</p><p>This extends to images. The sizes attribute is set per component based on layout context. Touch targets, font sizes, and spacing are part of the design system, not afterthoughts applied per page.</p><h3>The business side</h3><p>For most Australian businesses, the majority of first impressions happen on a phone. A prospective client finds your site, makes a judgement in seconds, on a small screen, probably distracted.</p><p>If the site loads slowly on mobile, the text is too small, or the navigation doesn’t work with thumbs, they leave. They don’t try again on a laptop. They go to the next search result.</p><p>Mobile-first responsive design isn’t a technical checkbox. It’s the experience that determines whether visitors become enquiries.</p><p>Little Dash builds responsive design into every component, not as a retrofit after the desktop version is signed off. If your mobile experience is costing you rankings and conversions, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a74ee1f42f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Publish in Payload, invalidate precisely in Next.js]]></title>
            <link>https://medium.com/@hello_82362/publish-in-payload-invalidate-precisely-in-next-js-e8711b8381e7?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8711b8381e7</guid>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Tue, 13 Oct 2026 09:36:01 GMT</pubDate>
            <atom:updated>2026-10-13T09:36:01.633Z</atom:updated>
            <content:encoded><![CDATA[<p>Every headless CMS site faces the same caching problem. You want aggressive caching for fast page loads and low server costs. But when someone publishes a change, the site needs to reflect it immediately.</p><p>Most setups pick one of two bad options. Short cache lifetimes, where content refreshes every 60 seconds, defeating the point of caching. Or full site rebuilds on every publish, which works until the site has a few hundred pages and every typo fix triggers a five-minute build.</p><p>We use cache tags to get precise invalidation without either compromise.</p><h3>How cache tags work</h3><p>Next.js supports two kinds of cache invalidation: path-based and tag-based.</p><p>Path revalidation clears the cache for a specific URL. Publish a blog post, call revalidatePath(&#39;/blog/post-slug&#39;), that page regenerates. Simple and direct.</p><p>But a blog post doesn’t only live at its own URL. It appears on the blog listing, in category archives, in “related posts” carousels on other pages, and in the sitemap. Path revalidation alone means tracking every URL that displays content from the thing you just changed. That list gets unmanageable.</p><p>Tag revalidation solves this. Instead of targeting URLs, you tag cached data by what it contains. The blog listing is tagged posts. The sitemap is tagged posts-sitemap. The carousel has its own tag. When a post is published, you revalidate those tags — and every cached fragment referencing that content type refreshes automatically.</p><h3>What our hooks do</h3><p>Every content type in Payload has collection hooks that fire on publish, unpublish, and delete. Each hook knows exactly which caches to invalidate.</p><p>A blog post publish revalidates the post’s URL, the posts sitemap tag, the archive categories tag, and the carousel tag. An unpublish also clears the old path so it returns a 404 instead of stale content. Globals like the footer revalidate a single tag that every page depends on, change the footer once, every page picks it up.</p><h3>The editorial experience this creates</h3><p>For the content team, they edit in Payload, hit publish, and the site reflects the change within seconds. No waiting for a build queue. No asking a developer to deploy. No “clear the cache” button.</p><p>Sitemaps update automatically. Carousels include the new content. Category archives reflect the change. Everything that should update, updates. Everything that shouldn’t, doesn’t.</p><p>This is what headless CMS architecture should deliver, the performance of aggressive caching with the freshness of a system that knows exactly what changed.</p><p>Little Dash builds platforms on Payload CMS and Next.js where caching, invalidation, and editorial workflows are handled from the architecture level. If your site is stuck choosing between stale content and slow rebuilds, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8711b8381e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our image pipeline: Payload CMS sizes, webp, and Next.js image]]></title>
            <link>https://medium.com/@hello_82362/our-image-pipeline-payload-cms-sizes-webp-and-next-js-image-408d1dd11c7d?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/408d1dd11c7d</guid>
            <category><![CDATA[core-web-vitals]]></category>
            <category><![CDATA[payload-cms]]></category>
            <category><![CDATA[image-optimization]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 02:46:01 GMT</pubDate>
            <atom:updated>2026-10-06T02:46:01.564Z</atom:updated>
            <content:encoded><![CDATA[<p>The hero image on your homepage is probably the single biggest factor in your Largest Contentful Paint score. And LCP is one of three Core Web Vitals that directly affect search rankings.</p><p>Most teams handle images by uploading whatever the designer exported and hoping the framework sorts it out. The result: a 1920px JPEG served to a 375px phone, no blur placeholder, no priority loading, and an LCP score that tanks the page’s search performance.</p><p>We built an image pipeline that handles this at the CMS level.</p><h3>What happens on upload</h3><p>Every image uploaded to Payload goes through a defined pipeline. Eight responsive sizes are generated, from 300w thumbnails to 1920w desktop assets, plus a dedicated 1200×630 OG crop for social sharing. Focal point is enabled so editors control where crops centre. Every size is converted to WebP at quality 90, typically reducing file size by 25–35% compared to JPEG at equivalent visual quality.</p><p>The OG crop is important because it connects to metadata architecture. When a page’s Open Graph image is requested, it pulls this dedicated asset rather than squashing a hero image into the wrong aspect ratio. Social previews should be intentional.</p><h3>How the frontend uses it</h3><p>Images render through Next.js Image with component-level sizes attributes based on layout context. A full-width hero gets different sizes than a card thumbnail. Without correct sizes, the browser downloads the largest available image regardless of viewport width.</p><p>Above-the-fold images get priority and fetchPriority=&quot;high&quot; so they start downloading immediately. Everything else lazy-loads. Quality is set to 100 at the component level because the CMS already handled compression during WebP conversion, double-compressing produces visible artifacts.</p><p>Every image gets a blur placeholder for perceived performance. Visitors see a low-resolution preview while the full image loads.</p><h3>The cache-busting detail most pipelines miss</h3><p>What happens when an editor replaces an image? If the URL doesn’t change, the CDN serves the old image until the cache expires, potentially days or weeks.</p><p>We append a cache-busting parameter from the media’s updatedAt timestamp. When the image is replaced, the timestamp changes, the URL changes, and every cache layer fetches the new version. The cache TTL stays aggressive (one year) because the URL itself changes on update.</p><p>Performance and freshness aligned, not traded against each other.</p><h3>What this means for Core Web Vitals</h3><p>LCP improves because above-the-fold images are priority-loaded, correctly sized, and served in WebP. CLS is avoided because Next.js Image reserves the correct aspect ratio before the image loads. Total page weight drops because mobile devices download mobile-sized images.</p><p>For editors, none of this is visible. They upload an image, optionally set the focal point, and the pipeline handles everything else. Performance as a system default, not a manual task.</p><p>Little Dash builds platforms on PayloadCMS and Next.js where image performance, structured data, and Core Web Vitals are handled from the architecture level, not optimised after the build. If your site’s images are dragging down performance, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=408d1dd11c7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why our own review schema won’t earn Google stars]]></title>
            <link>https://medium.com/@hello_82362/why-our-own-review-schema-wont-earn-google-stars-ab2d771e8432?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab2d771e8432</guid>
            <category><![CDATA[google-reviews]]></category>
            <category><![CDATA[json-ld-structured-data]]></category>
            <category><![CDATA[structured-data]]></category>
            <category><![CDATA[technical-seo]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 23:51:01 GMT</pubDate>
            <atom:updated>2026-09-29T23:51:01.517Z</atom:updated>
            <content:encoded><![CDATA[<p>We built a structured data system that automatically generates Review JSON-LD from our testimonials block. Every testimonial becomes a valid Review object with author, rating, and review body. It passes Google&#39;s Rich Results test without errors.</p><p>And Google will never show review stars for it.</p><h3>The rule most people miss</h3><p>Google’s guidelines are explicit: review stars in search results are not available when the entity being reviewed operates the website. Our testimonials have itemReviewed set to Little Dash,our own organisation. Google treats this the same way it treats a restaurant putting &quot;5 stars&quot; on its own menu.</p><p>This applies regardless of whether the reviews are genuine. Ours are — from real clients about real projects. But the policy isn’t about authenticity. It’s about independence. Google trusts third-party platforms because they control the submission and moderation process. Your own website doesn’t provide that independence signal.</p><h3>Where stars actually come from</h3><p>Three paths, none of which involve self-hosted schema.</p><p>Google Business Profile, the primary source for local businesses. For an Australian service business, this is the most impactful channel for review visibility.</p><p>Third-party review platforms, Clutch, Trustpilot, G2. These operate independently from your business, which is what Google requires.</p><p>Aggregate ratings from independent sources, consistent listings across multiple review platforms, matched by NAP (name, address, phone).</p><h3>Why we kept the schema anyway</h3><p>Knowing Google won’t show stars, we deliberately kept the Review JSON-LD. The schema still helps search engines and AI tools understand what the testimonials are, clearly typed Review objects, not just a wall of rich text. For AI-powered search tools answering “what do clients say about Little Dash,” the structured data gives them clean, extractable answers.</p><p>The testimonials page is also a conversion asset. Real client feedback, clearly structured. The Review schema doesn’t earn Google stars, but it makes the page more useful for every other channel.</p><h3>The honest strategy</h3><p>Google Business Profile is our priority for review stars. We’ve added a Google review link to the testimonials page so clients can easily leave the same feedback on GBP. The on-site testimonial drives conversion. The GBP review drives search visibility. Same client, different channels, different purposes.</p><p>This is the honest version of review strategy: don’t overclaim what self-hosted reviews can do in search, and invest in the channels that actually earn the signals Google values.</p><p>Little Dash builds platforms on PayloadCMS and Next.js where structured data is generated automatically from the CMS, including knowing what it can and can’t earn in search. If your structured data strategy needs an honest audit, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab2d771e8432" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FAQ pages that answer engines can actually use]]></title>
            <link>https://medium.com/@hello_82362/faq-pages-that-answer-engines-can-actually-use-795d79825f88?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/795d79825f88</guid>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Wed, 23 Sep 2026 01:21:01 GMT</pubDate>
            <atom:updated>2026-09-23T01:21:01.558Z</atom:updated>
            <content:encoded><![CDATA[<p>Every business website has an FAQ page. Almost none of them are doing anything useful.</p><p>The typical FAQ is a single list of questions dumped onto a page with no grouping, no structure, and no thought about how the content gets consumed by search engines or AI tools. It sits in the footer navigation, rarely gets updated, and contributes almost nothing to the site’s search visibility.</p><p>That’s a waste, because FAQ content directly answers the questions your prospects are actually asking. The problem isn’t the content, it’s how it’s structured.</p><h3><strong>Treating FAQ as architecture, not a page template</strong></h3><p>We model FAQ as a content architecture decision in Payload CMS. Questions are stored as their own collection, grouped by topic (platforms, delivery, pricing, support), and surfaced wherever they’re needed, the main FAQ page, relevant service pages, blog post sidebars.</p><p>Each group gets an anchor ID, so you can deep-link directly: `/frequently-asked-questions#pricing`. This is valuable for sales conversations, internal linking from blog posts, and AI tools that cite specific sections.</p><p>The questions render as accessible accordions, collapsed by default, expandable on click. But the answers are in the HTML whether the accordion is open or not. If the answer only loads when clicked, search engines and AI tools can’t see it. The content needs to be in the DOM from the first render.</p><h3><strong>The structured data layer</strong></h3><p>Each FAQ group automatically generates FAQPage schema, the markup Google uses for those expandable Q&amp;A dropdowns in search results. Because the content is structured in the CMS (not free-form rich text), the schema generates from the content itself. Add a question, and the FAQPage schema updates automatically.</p><p>One detail most implementations miss: Google only accepts one FAQPage per URL. Multiple FAQ groups on a single page need to collapse into a single FAQPage with a combined question array, not one per group.</p><h3><strong>The AI layer</strong></h3><p>This connects to the llms.txt approach we wrote about recently. AI tools answering questions like “how much does a headless CMS build cost” are looking for clear, direct answers they can cite. A well-structured FAQ page with grouped topics and anchor IDs is exactly what these tools need.</p><p>Our FAQ page is referenced directly in our llms.txt file. When an AI tool follows that link, it finds content already organised by topic with clear question-answer separation. The anchor IDs mean the tool can cite a specific section rather than pointing at the whole page.</p><h3><strong>FAQ as a sales tool</strong></h3><p>Well-structured FAQ content works in sales conversations too. “How does your pricing work?”, here’s a direct link to the pricing FAQ group rather than typing out the answer. The same page serves organic search, AI citations, and direct sales.</p><p>The investment is in the architecture, not the volume. A well-structured page with twenty questions works harder than a dumped list of fifty.</p><p>— -</p><p>Little Dash builds content architecture on PayloadCMS where FAQ pages, structured data, and machine readability are part of the platform — not afterthoughts. If your FAQ page is sitting in the footer doing nothing, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=795d79825f88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We wrote an llms.txt for our agency site, here’s what we put in it]]></title>
            <link>https://medium.com/@hello_82362/we-wrote-an-llms-txt-for-our-agency-site-heres-what-we-put-in-it-0a24463e84d0?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a24463e84d0</guid>
            <category><![CDATA[seo-tips]]></category>
            <category><![CDATA[structured-data]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 00:26:01 GMT</pubDate>
            <atom:updated>2026-09-16T00:26:01.357Z</atom:updated>
            <content:encoded><![CDATA[<p>A growing number of people are asking AI tools questions that used to go to Google. “Who builds PayloadCMS sites in Australia.” “What does a headless CMS build cost.” “Which agencies in Brisbane specialise in Next.js.”</p><p>These tools don’t crawl the web the way search engines do. They’re looking for clear, structured information they can cite and summarise. And most business websites give them nothing useful to work with.</p><p>So we shipped an `llms.txt` file.</p><h3><strong>What it is</strong></h3><p>`llms.txt` is a plain text file at the root of your website, like `robots.txt`, but for AI crawlers. It gives language models a structured summary of your business: who you are, what you do, where you’re based, who you work with, and where to find more detail.</p><p>It’s not an official standard yet. There’s no guarantee every AI tool reads it today. But the cost of adding it is near zero, and when these tools do look for structured business information, yours is there and accurate.</p><h3><strong>What we put in ours</strong></h3><p>We structured it around the information an AI tool would need to describe Little Dash accurately in a recommendation.</p><p>A business summary with entity clarity, Brisbane-based web development studio, not a fitness brand or a SaaS product. Service pillars with URLs, brief descriptions, and indicative pricing. Completed projects with short descriptions for concrete evidence. Links to FAQ, about, testimonials, and contact pages. Social profiles for verification.</p><p>The key principle: factual, not promotional. AI tools aren’t looking for marketing copy, they’re looking for extractable facts.</p><h3><strong>The part most people miss</strong></h3><p>The file itself is just a pointer. It only works if the pages it links to are clear, well-structured, and genuinely informative.</p><p>Our FAQ page is modelled as grouped, topic-based accordions with anchor IDs, not a dump of random questions. Our service pages describe what we deliver with enough specificity for an AI to extract real answers. Our pillar pages cover topics comprehensively enough to be cited as sources.</p><p>llms.txt tells AI tools where to look. What they find when they get there is what determines whether you’re cited accurately or ignored entirely.</p><h3><strong>What we don’t claim</strong></h3><p>AEO is not like SEO. There’s no Search Console for AI citations. You can’t reliably track when an AI tool recommends you. The standards are emerging and the tools are changing every few months.</p><p>What we do know: clear, structured, factual content about your business is never wasted, whether it’s consumed by Google, an AI tool, or a human reading your site. We’re treating llms.txt as one piece of a broader content architecture strategy, not a magic bullet.</p><p>The cost is near zero. The potential upside is showing up in the fastest-growing discovery channel in search.</p><p>— -</p><p>Little Dash builds platforms on PayloadCMS and Next.js where content architecture, structured data, and machine readability are part of the build, not afterthoughts. If you’re thinking about how your website shows up in AI-powered search, <a href="https://meetings-ap1.hubspot.com/little-dash/meet">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a24463e84d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When to rebuild a platform (and when to resist)]]></title>
            <link>https://medium.com/@hello_82362/when-to-rebuild-a-platform-and-when-to-resist-a4aa404a1c3e?source=rss-9f70aa81d44c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4aa404a1c3e</guid>
            <category><![CDATA[website-redesign]]></category>
            <category><![CDATA[rebuild-website]]></category>
            <category><![CDATA[website-development]]></category>
            <dc:creator><![CDATA[Christopher Nowlan]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 08:06:00 GMT</pubDate>
            <atom:updated>2026-09-09T08:06:00.814Z</atom:updated>
            <content:encoded><![CDATA[<p>The conversation about rebuilding a platform usually starts with frustration. The site is slow. The CMS is painful. The design feels dated. Someone says “we should just start fresh” and suddenly there’s a proposal on the table for a six-figure rebuild.</p><p>Sometimes that rebuild is exactly the right move. Sometimes it’s an $80,000 solution to a $15,000 problem. The hard part is telling the difference.</p><h3>When a rebuild is warranted</h3><p>There are four signals that a platform genuinely needs replacing rather than improving.</p><p>The architecture can’t support what you need, the CMS doesn’t model your content properly, you’re cramming structured data into rich text fields, and the content model can’t be fixed without starting over. Performance has a structural ceiling, you’ve optimised everything you can and the site is still slow because the problems are architectural. The cost of maintenance exceeds the cost of rebuilding, plugin conflicts, security patches breaking features, custom workarounds needing constant attention. Or the platform blocks your business strategy, you need multi-channel delivery, editorial workflows, or integrations that the platform can’t support.</p><p>When any of these are true, a rebuild is a strategic investment, not a reaction to frustration.</p><h3>When a rebuild isn’t the answer</h3><p>A site can feel broken when the real issue is content that hasn’t been updated in two years. A slow page doesn’t mean the whole site needs rebuilding. A painful editing experience might be solved by CMS configuration, not a new CMS.</p><p>The honest test: list every problem with the current platform and ask “is this fixable on the current platform?” and “what would fixing it cost versus rebuilding?” Many problems that feel structural are actually operational.</p><p>A new platform is also only as good as the team using it. If the content team struggles with the current CMS, a more complex headless CMS with more flexibility might make things worse without proper onboarding.</p><h3>Making the case internally</h3><p>Decision-makers respond to ongoing cost, not frustration. “We spend $X per month maintaining a platform that limits our ability to do Y” is stronger than “the site feels old.”</p><p>Define what the new platform needs to do differently, not a feature list, but a capabilities gap. And present the alternatives honestly. Sometimes the right recommendation is targeted improvements at a fraction of the rebuild cost. Presenting this option builds credibility, and if the rebuild is genuinely the right move, the comparison makes the case stronger.</p><h3>The pattern</h3><p>The worst rebuilds are reactive, triggered by frustration with no clear requirements. The best rebuilds are strategic, a defined capabilities gap, a documented scope, and a discovery phase that turns “we need something better” into a specific plan with a fixed quote.</p><p>A rebuild is the right answer when the platform can’t grow with the business. It’s the wrong answer when the problem is content, process, or a fixable limitation being treated as a fundamental one.</p><p>Little Dash builds platforms on PayloadCMS and Next.js for businesses that need senior technical capability without an internal team. If you’re considering a rebuild — or wondering whether you actually need one <a href="https://meetings.hubspot.com/chris-nowlan/little-dash-discovery-call">book a free discovery call</a> or visit <a href="https://www.littledash.com.au/">littledash.com.au</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4aa404a1c3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>