Why I separate tutorials and income reports in AFFINGER5
A blog can become difficult to manage when every post is treated as the same kind of content. Tutorials, product reviews, personal experiments and monthly income reports may all be published in WordPress, but readers approach them with different expectations. I use AFFINGER5’s custom post types to create a clearer divide between practical teaching content and the financial record of running a blog.
This structure also reflects how I work as a freelance blogger. A tutorial should remain useful months or years after publication, while an income report is tied to a particular month, campaign or business decision. Keeping those formats separate makes the site easier to browse, simplifies internal linking and gives each content group a more suitable layout.
Why standard blog posts became limiting
At first, publishing everything as a normal post seemed efficient. WordPress made it easy to add a title, write the article and assign categories or tags. Over time, however, tutorials and income reports began competing inside the same chronological archive. A detailed guide could quickly disappear beneath a newer earnings update, even when the guide was more valuable to search visitors.
The problem was not simply visual. The two formats need different introductions, calls to action and supporting information. A tutorial may require a table of steps, screenshots, plugin settings and troubleshooting notes. An income report needs dates, traffic figures, revenue sources, expenses and a short explanation of what changed. Forcing both into one template created unnecessary editing work.
Custom post types give each format a defined place in the content system. Instead of relying on a complicated category structure, I can maintain a tutorial archive and an income-report archive with their own navigation paths. This is especially helpful when a site covers several subjects, such as WordPress, SEO, affiliate marketing and theme customisation.
How I use custom post types in AFFINGER5
My tutorial content is designed as a long-term knowledge base. Each article explains a task or process, such as configuring AFFINGER5, improving an affiliate page or moving a WordPress site. The format places the main answer near the beginning, followed by clear steps, examples and notes about mistakes that can affect the result.
Income reports use a different editorial rhythm. They document what happened during a specific period, why revenue rose or fell, which affiliate programmes performed well and what I plan to test next. Readers are not usually looking for a timeless technical answer in these posts. They want context, honest figures and a realistic account of the work behind the numbers.
AFFINGER5 helps me keep the visual presentation consistent while allowing the information hierarchy to change. I can use a more instructional layout for tutorials and a more journal-like structure for reports. Shared branding, typography and navigation still make the website feel unified, but visitors can immediately recognise the type of page they are reading.
The separation also makes editing less error-prone. A tutorial can have its own reusable opening, related-article area and update note, while a report can include a period label and a standard revenue breakdown. This saves time when publishing regularly and reduces the temptation to copy a layout that does not suit the content.
Better navigation for readers and search engines
A reader arriving from Google often has a specific intention. Someone searching for an AFFINGER5 sidebar setting wants instructions, not a monthly account of affiliate income. Someone searching for a blogging income report may be interested in the business journey rather than a step-by-step WordPress solution. Separate content types help me respect that intent from the first screen.
The archives provide a useful secondary route after the visitor finishes an article. A tutorial reader can move to another guide in the same subject area, while a reader interested in the business side of blogging can browse reports by year or month. This creates a stronger internal-linking system than placing every article in one long feed.
The approach suits Australian readers who may be browsing during a commute on the Sydney train network or checking a quick answer between client appointments. Clear labels reduce the amount of scrolling and guessing required. A visitor from Brisbane or Perth can tell whether a page offers a practical fix or a personal business update before investing time in it.
Search engines also receive clearer signals when related pages are organised consistently. Custom post type archives, descriptive taxonomies and contextual links can reinforce topical relevance. They do not guarantee rankings, but they make the site architecture easier to understand and maintain as the content library grows.
Different content needs different conversion paths
A tutorial usually leads towards a relevant tool, theme feature or related guide. The recommendation should appear where it solves a problem described in the article. For example, an explanation of targeted affiliate placements can naturally point readers towards custom sidebar strategies when the page discusses displaying offers according to content context.
An income report has a softer conversion path. It may mention an affiliate product that produced results, but the article should explain the circumstances rather than push a sale at every opportunity. The value comes from transparency: readers can see the traffic source, publishing effort, conversion pattern and limitations of the result.
Separating the post types helps me control those differences. Tutorial pages can use focused calls to action, comparison boxes and links to implementation guides. Reports can include a concise summary of lessons learned, followed by links to the actual tutorials or tools involved. This keeps monetisation relevant instead of making every page feel like an advertisement.
That distinction matters in the Australian affiliate market, where audiences often respond better to plain, practical language than exaggerated claims. Terms such as “a fair bit,” “good value” and “worth a look” can sound more natural than aggressive sales copy when the recommendation is genuinely useful. Trust is particularly important when income figures are visible.
Reporting figures without confusing the archive
Income reports need consistent definitions. I record the reporting period, traffic sources and revenue categories so that readers can compare one month with another. Affiliate commissions, advertising income and digital product sales should not be blended into one impressive-looking total without explanation. Expenses and refunds also need to be acknowledged where relevant.
Australian business details can add another layer of complexity. Revenue may be shown in Australian dollars, US dollars or another currency depending on the affiliate network. Exchange rates can change the apparent result, and an Australian blogger may also need to think about an ABN, GST registration thresholds and whether a payment is business income. I make it clear when a figure is gross revenue rather than money available after tax.
The custom post type gives these reports a stable home without allowing them to dominate the main tutorial feed. A dated archive can show the progression from an early side project to a more organised freelance business. At the same time, evergreen guides remain discoverable through topic archives and search traffic.
This separation also protects the usefulness of old reports. A figure from 2019 may be historically interesting but should not appear to be current advice about affiliate rates or advertising performance. Date labels, archive titles and explanatory notes help readers understand the difference between an account of past results and a present-day tutorial.
A practical structure for maintaining both types
The system works best when the publishing rules are simple. I decide the content type before drafting, then use a matching title format, introduction and category structure. This prevents a report from slowly turning into a tutorial or a guide from becoming a diary entry about monthly traffic.
My basic workflow includes the following checks:
- Assign every draft to either the tutorial or income-report post type before writing.
- Use separate archive labels so visitors can browse guides and reports independently.
- Add dates, currency and revenue definitions to every income report.
- Link tutorials to related tutorials before adding commercial recommendations.
- Review old reports for expired affiliate links, outdated rates and discontinued tools.
- Keep AFFINGER5 styling consistent while changing the page structure to suit the content.
I also keep the taxonomy controlled. A small group of useful subjects, such as WordPress, SEO, affiliate marketing and theme customisation, is more helpful than dozens of near-duplicate tags. Income reports can use year and period labels, while tutorials can use task-based subjects. This gives the archive enough detail without creating thin pages that offer little value.
What this setup has taught me about blogging
The biggest lesson is that content management is part of content strategy. A blog is easier to grow when the publishing system reflects the reader’s needs. Custom post types are not a shortcut to better rankings or higher commissions, but they remove friction from planning, writing and updating.
They have also helped me be more honest about the difference between education and evidence. A tutorial explains what I believe will help someone complete a task. An income report shows what happened in my own circumstances, with all the variables that influenced the result. Treating those formats separately makes it harder to present a personal outcome as a universal promise.
For a blogger working across Australian time zones, client work and changing affiliate markets, that clarity is valuable. Whether I am publishing from Okinawa, reviewing a WordPress setting or recording a month of freelance income in AUD, the appropriate content type gives the material a clear context.
AFFINGER5’s custom post types have therefore become part of my editorial discipline rather than just a design feature. Tutorials remain useful resources, income reports remain transparent records, and both can support the wider site without confusing their purpose.