WP to XML

Tag: XML feed

  • Case Study 11: Google Shopping XML Feed for WordPress Custom Fields: Whitewater Tours Case Study

    Project Overview

    A client from Whitewater Tours needed a Google Shopping XML product feed for approximately 50 products on their WordPress website.

    The website used custom WordPress fields to store product information, and the client wanted that information converted into an XML feed that could be used with Google.

    The project was a good example of how a custom XML feed can be built around an existing WordPress data structure rather than requiring the client to manually maintain a separate product feed.

    Project Requirements

    The main requirements were:

    • Create a Google Shopping XML product feed.
    • Generate the feed from WordPress custom fields.
    • Support approximately 50 products.
    • Make the feed accessible through a dedicated XML URL.
    • Ensure newly added products could automatically appear in the feed.
    • Provide a solution suitable for submission to Google Merchant Center.

    The initial project budget was $50, with a three-day delivery requirement.

    Understanding the Client’s WordPress Structure

    The client explained that the products were already managed through WordPress and that the required information was stored in custom fields.

    Instead of creating a completely separate product database, the approach was to work with the existing WordPress content and transform the available product information into the required XML feed structure.

    This is an important consideration when developing feeds for WordPress websites.

    A feed should ideally work with the website’s existing data rather than forcing the site owner to maintain product information in multiple places.

    Creating the Custom XML Feed

    A custom WordPress XML feed solution was developed specifically for the website.

    The feed was designed to collect the relevant product information from WordPress and make it available through an XML endpoint.

    The resulting feed was intended to provide a direct URL that could be supplied to Google Merchant Center.

    The client also asked whether the feed would automatically include a new product when it was added to the website.

    The answer was yes.

    This meant the client would not need to manually recreate the XML feed every time a new product was published.

    WordPress Plugin Installation

    Because the website was running as a WordPress multisite, the plugin installation required some additional coordination.

    Initially, the required permissions were not available for installing the plugin directly.

    The client therefore uploaded the provided plugin package, after which the feed could be tested and refined.

    This is a common practical issue when working on client websites: the technical implementation may be straightforward, but access permissions and hosting configuration can affect the development workflow.

    Testing and Refinement

    The plugin was not considered finished immediately after installation.

    The client asked whether the work was complete once the plugin had been uploaded.

    The response was that the feed still needed to be checked and refined before being considered final.

    The goal was to make sure that the generated XML could be used as the feed source and that the client could subsequently submit the feed URL to Google Merchant Center.

    The client also confirmed that they would test the implementation and report any issues.

    Automatic Product Updates

    One of the useful features of the implementation was that the XML feed was connected to the site’s WordPress product data.

    The client specifically asked:

    If a new product is added, will it auto go to the XML feed?

    The answer was yes.

    This makes a custom feed considerably more useful for an active website because the feed can continue to reflect the site’s product catalog without requiring the site owner to manually edit an XML file every time a product is added.

    Expanding Beyond Google Shopping

    After the initial XML feed work, the client asked about another Google integration: Google Things to Do.

    This introduced a different type of feed requirement involving event and activity information.

    The discussion moved toward JSON feeds and customized data for individual events.

    The client was informed that the data structure on the website would need to be customized for each event and that the work could be started with a single event to verify the output before expanding the implementation.

    This demonstrated another advantage of working with custom feed development: once the underlying WordPress data and feed requirements are understood, similar structured-data integrations can be evaluated and developed around the same website.

    A Later Check: Feed Endpoint No Longer Available

    More than a year after the original implementation, the old Google feed URL was checked again:

    whitewatertours.com/google.xml

    The endpoint is currently returning a Page Not Found response.

    This does not necessarily mean that the original feed implementation failed. Websites are frequently redesigned, plugins are removed, URLs are changed, or WordPress configurations are modified over time.

    Because the current endpoint is no longer available, the next step is to determine whether the client still requires the Google Shopping feed and, if so, what has changed on the website since the original implementation.

    A follow-up was therefore sent to the client offering to investigate the issue and restore the feed if it is still required.

    Key Takeaways

    This project highlights several important considerations when creating custom XML feeds for WordPress websites.

    1. Work With Existing WordPress Data

    Using the website’s existing custom fields can eliminate unnecessary duplication and allow the feed to stay connected to the site’s product information.

    2. Automate Feed Updates

    Automatically generating the XML output means that new products can be incorporated into the feed without manually editing an XML file.

    3. Consider WordPress Multisite During Development

    Multisite installations can introduce additional permission and plugin-installation considerations that should be accounted for before development begins.

    4. Test Before Submitting the Feed

    A feed should be checked and refined before its URL is submitted to Google Merchant Center.

    5. Feed Maintenance Matters

    Even a working feed can become unavailable later because of website changes, plugin removal, URL changes, migrations, or other configuration changes.

    For this reason, an XML feed should be treated as part of the website’s ongoing technical infrastructure rather than a completely one-time task.

    Conclusion

    The Whitewater Tours project started with a straightforward requirement: convert approximately 50 WordPress products stored using custom fields into a Google Shopping XML feed.

    A custom WordPress feed solution was developed, installed on the client’s multisite environment, and prepared for testing and use with Google Merchant Center.

    The project also opened the door to discussing additional structured-data integrations such as Google Things to Do.

    The later discovery that the original /google.xml endpoint is no longer available also illustrates an important aspect of feed development: ongoing website changes can affect previously working integrations.

    For businesses relying on XML feeds for Google or third-party platforms, periodic testing of the feed URL is therefore a useful part of website maintenance.

  • Case Study 10: Building and Maintaining a Multi-Portal Real Estate Feed System for WordPress

    From One Custom XML Feed to a Multi-Portal Property Distribution System

    Real estate websites often need to distribute property listings to multiple portals, marketplaces, advertising platforms, and property aggregators. The challenge is that each platform can require a completely different XML, JSON, or CSV structure, while the source website may use a WordPress theme such as Houzez with custom fields, taxonomies, multilingual data, and different measurement formats.

    This case study describes a long-term project for a real estate website using WordPress, Houzez, WP All Import, and WP All Export.

    The project began with a relatively small requirement: fixing several fields in an existing WP All Export template for a property portal. Over time, the requirement expanded into a collection of custom feeds and ongoing feed maintenance.

    The initial client requirement included generating property feeds for external portals while continuing to use the existing WP All Export setup where possible. The client specifically needed help with image URLs, furniture/status values, and conversion of Thai land measurements such as square wah and rai into square metres.

    The Initial Challenge

    The client’s WordPress website contained property data in different formats.

    Some of the major challenges included:

    • Multiple property images needed to be output as individual URL elements.
    • Values such as “Furnished” needed to be cleaned before being sent to the destination portal.
    • Status values required transformation.
    • Land measurements could be stored as square wah, rai, or combined formats such as Rai-Ngan-Wah.
    • Property types needed to be mapped from WordPress parent/child categories into the destination portal’s terminology.
    • Virtual-tour information needed to be converted into the format required by the portal.
    • Different portals required different XML structures.

    The first approach was to see whether the existing WP All Export template could be modified rather than immediately replacing it with a custom plugin. A custom plugin was kept as the fallback option if the existing export system could not handle the requirements.

    This approach helped avoid unnecessary redevelopment and allowed the existing WordPress workflow to remain part of the solution.

    Phase 1: Proppit XML Feed

    The first major deliverable was a custom XML feed for Proppit.

    The feed was initially developed around the client’s existing property data and then refined based on real output and feedback.

    One important requirement was converting land measurements and removing decimal values from both land area and floor area. The feed was subsequently updated to round floorArea and plotArea.

    Complex Property Data Mapping

    The project involved more than simply copying WordPress fields into XML tags.

    For example, property types had to be interpreted according to the destination portal’s requirements. Later revisions included distinguishing between residential and commercial property types and mapping categories such as:

    • House
    • Condo
    • Townhouse
    • Shophouse
    • Office
    • Hotel
    • Factory
    • Retail space

    The client provided examples where a property could have multiple WordPress categories, requiring custom logic to determine which category should become the primary destination value.

    This illustrates an important aspect of custom feed development: source taxonomy and destination taxonomy rarely match one-to-one.

    Diagnosing WP All Export

    An interesting technical problem appeared when the WP All Export template worked in Preview mode but failed during the actual export.

    Testing showed that individual properties could be exported successfully and that reducing the number of XML tags allowed all 88 properties to process. The investigation indicated that the problem was likely related to the number of database queries and server resource limitations during the larger export.

    The recommendation was to investigate hosting limits such as maximum execution time and memory rather than incorrectly blaming the property data or custom functions.

    Meanwhile, the custom feed continued to provide a working alternative.

    This was an important distinction:

    A feed can be logically correct while the export mechanism used to generate it is still limited by server resources.

    Virtual Tour and Feed Formatting Fixes

    The Proppit feed later required the virtual-tour field to contain a direct link rather than embed code.

    The feed was updated accordingly.

    A further issue appeared where one property was receiving an incorrect virtual-tour base URL because different properties could use different virtual-tour providers.

    The feed logic was adjusted so that the property-specific virtual-tour URL could be handled correctly rather than applying one universal URL to every listing. The client confirmed that the corrected virtual-tour link was displaying properly.

    Expanding Into Multiple Feeds

    After the initial Proppit implementation, the project expanded significantly.

    The client requested additional feeds for other real estate platforms and advertising systems, including:

    • Thailand Housing Market
    • Baan Finder
    • Living Insider
    • Facebook Commerce Manager
    • Google-related feeds
    • Google Ads real estate CSV
    • Green-Acres
    • Nestopa
    • Propertyhub JSON
    • XML2U / Properstar-related distribution

    The client also maintained a Google Sheet to track the different feeds and requirements.

    This changed the nature of the work from a one-off XML customization into an ongoing multi-feed property distribution system.

    Google Feed and Local Inventory

    The Google feed required additional destination-specific fields and formatting.

    Updates included:

    • Resolving line-break formatting.
    • Removing an unwanted price prefix.
    • Adding store_code.
    • Adding quantity.
    • Creating a separate feed for local inventory because the destination required a different filename.

    The primary Google feed and Proppit feed were updated accordingly.

    A separate local inventory feed was subsequently created:

    google_local_inventory_xml_feed.xml

    The feed was also repaired after a PHP version change caused the XML feeds to stop working. The client had moved the hosting environment to PHP 8.2.4, and the feed plugins were upgraded to work with the newer environment.

    This demonstrated another recurring challenge with WordPress feed systems: hosting and PHP environment changes can affect custom feed code even when the property data itself has not changed.

    Facebook Commerce Manager Feed

    The project also expanded into a Facebook Commerce Manager XML feed.

    The feed required destination-specific handling for fields such as:

    • Property type
    • Pet policy
    • Area size
    • Neighborhood
    • Address information
    • Page ID
    • Security deposit
    • Utilities
    • Video

    The feed was revised several times based on Facebook’s validation feedback. Eventually, the video field was removed because the destination required a direct downloadable video URL rather than a normal video-hosting page URL.

    This is another example of why feed development is not simply an XML-generation exercise. The destination platform’s validation rules must be incorporated into the transformation logic.

    Baan Finder and Living Insider

    The next stage involved creating feeds for Baan Finder and Living Insider.

    Baan Finder required more complex property-type mapping.

    For example, a property categorized as commercial on the WordPress website could still need to be mapped to SHOPHOUSE, HOTEL, FACTORY, OFFICE, or another destination-specific type depending on information contained in the title or description.

    Living Insider introduced another layer of complexity around land measurements.

    Different fields were required depending on property type, including:

    • Square metres
    • Square wah
    • Rai
    • Ngan
    • Wah
    • Separate land-area components
    • Thai and English titles/descriptions
    • Condo-specific values
    • Multiple image URLs

    The client specifically identified cases where a value such as 174 square wah needed to be separated into the appropriate Rai/Ngan/Wah fields rather than simply placing the entire number into one field.

    Green-Acres Integration

    In 2025, another feed was added for Green-Acres.

    The feed was developed as a dedicated XML integration and subsequently updated with destination-specific fields including:

    • English title
    • Province
    • Sub-district/district
    • Property ID
    • Favorite status
    • Included fees
    • Agency rate type

    After submission, the destination platform reported a video URL problem. The video URL issue was diagnosed and corrected, after which the feed was reported as working.

    Long-Term Feed Maintenance

    One of the most interesting aspects of this project is that the work did not end after the initial feed development.

    As the website, destination platforms, hosting environment, and property data changed, new requirements continued to appear.

    Examples included:

    • New destination validation rules.
    • Changes to property classifications.
    • New PHP versions.
    • Different language requirements.
    • Changes to virtual-tour providers.
    • New property filtering requirements.
    • Feed performance concerns.
    • Listing limits imposed by external platforms.
    • Changes in external APIs.
    • New image-handling requirements.

    For example, in 2025 the client became concerned about the number of listings being refreshed on Properstar. A strategy was discussed to change only a limited number of property IDs per day instead of changing all IDs simultaneously. The proposed approach was approximately 15 listings per day for a 500-listing cycle.

    Later, Nestopa introduced a limit on the number of listings displayed under its free plan, leading to another requirement to prioritize particular property listings and control how frequently listing IDs changed.

    This shows how a feed system can evolve into a business-rule engine, rather than remaining a static XML generator.

    Feed Filtering and Automation

    As the number of feeds increased, the client wanted greater control over which properties were included.

    The proposed feed-management logic included filtering by:

    1. Property ID prefixes.
    2. Minimum sale price.
    3. Minimum rental price.
    4. Custom fields.
    5. Specific properties to include.
    6. Specific properties to exclude.
    7. Property status.
    8. Other feed-specific conditions.

    For example, a custom field such as fave_luxury = Yes could be used to select properties for a particular luxury-property feed.

    This approach provided much greater flexibility than hard-coding a completely different selection rule into every feed.

    Performance Became a Separate Challenge

    As the number of properties and feeds increased, feed-generation performance became an important concern.

    The client reported that some XML URLs could take several seconds to load and, in some cases, make the browser appear unresponsive.

    The website developer subsequently implemented Redis caching for the feed outputs. According to the project discussion, the site was generating approximately 15 XML/JSON feed outputs from more than 800 properties and many custom fields. The caching layer was intended to make repeated feed requests significantly faster and automatically refresh the cache after imports.

    The project therefore evolved beyond field mapping into considerations involving:

    • Database queries
    • Feed generation performance
    • Caching
    • Import/export workflows
    • Background processing
    • Feed refresh cycles

    Handling Large Feeds

    Another scalability issue emerged when Living Insider imposed a limit of 1,000 records per XML or CSV file.

    Instead of allowing the feed to grow indefinitely, the proposed solution was to introduce pagination so the listings could be divided into multiple parts.

    This is a useful example of designing around an external platform’s technical limitations rather than trying to force the destination to accept an oversized feed.

    Land Measurement Standardization

    The project eventually exposed a larger architectural issue: property data from different agencies did not use a consistent land-measurement format.

    Some providers supplied:

    • Square wah
    • Square metres
    • Rai
    • Rai + square wah
    • Rai + Ngan + square wah

    The client wanted to establish a consistent base measurement that could then be converted into other units.

    The requirement included creating import-side PHP logic so that incoming data could be normalized before it was used by the different feeds. The client specifically identified mixed-data providers such as Perfect Homes and Isara Real Estate as requiring special handling.

    This was an important shift from feed-level conversion to data normalization at the source/import level.

    Once data is normalized properly, multiple feeds can use the same underlying property values instead of implementing independent conversion logic repeatedly.

    Extending the System Beyond XML

    The project also expanded beyond traditional XML feeds.

    The client wanted to generate CSV data for a video-generation platform called CreateOMate, with the eventual goal of connecting the data to automation tools for social media publishing.

    The CSV needed to contain:

    • Individual photo URLs in separate columns.
    • A specific location structure.
    • Child property categories rather than parent/child category strings.
    • Conditional price formatting.
    • Potential HTML cleanup.

    The existing WP All Export template was modified using PHP functions to support these requirements.

    This demonstrated that the same WordPress property database could serve many different downstream purposes:

    Website → XML feeds → JSON feeds → CSV exports → advertising → social-media content

    What Made This Project Challenging?

    The biggest challenge was not creating XML syntax.

    The real difficulty was translating one complex real estate database into multiple destination-specific data models.

    The same property could require different:

    • Property types
    • Measurement units
    • Language values
    • Address structures
    • Image formats
    • Video formats
    • Status values
    • Price formats
    • Filtering rules
    • Required fields
    • Optional fields

    A field that worked correctly for one destination could be wrong for another.

    For example, HTML formatting could be useful in one feed but unacceptable in another. Similarly, a universal property-type rule could create incorrect classifications when a property had multiple categories.

    The project therefore required continuous validation against the actual destination requirements.

    Results

    The project evolved from a single custom XML-feed requirement into a long-term feed-development and maintenance relationship.

    The conversation records show work involving multiple destination feeds and formats, including Proppit, Google, Facebook, Thailand Housing Market, Baan Finder, Living Insider, Green-Acres, Nestopa, Propertyhub, and XML2U/Properstar-related integrations.

    The client repeatedly returned with additional feed requirements and described the collaboration positively. At one point, after multiple feed updates, the client stated that it was “great to have been able to make this contact” and asked to continue with additional feeds.

    The relationship subsequently continued into later years with additional feed modifications, filtering, performance, listing-refresh, and data-normalization requirements.

    Key Lessons From the Project

    1. Start With the Existing System

    The initial goal was not to replace WP All Export unnecessarily. The existing workflow was investigated first.

    This can reduce development time and preserve the client’s familiar workflow.

    2. Normalize Data Where Possible

    Repeated conversion logic across individual feeds can become difficult to maintain.

    Standardizing data during import can make downstream feeds significantly easier to manage.

    3. Every Portal Has Different Rules

    There is no universal “real estate XML feed.”

    Each destination may have different requirements for:

    • Categories
    • Measurements
    • Images
    • Descriptions
    • Languages
    • Videos
    • Pricing
    • IDs
    • Filtering

    4. Feed Development Requires Real-World Testing

    A feed can be valid XML and still be rejected by the destination.

    The project repeatedly required testing against actual portal feedback and adjusting the mapping accordingly.

    5. Scaling Changes the Architecture

    As the number of properties and feeds grows, performance becomes important.

    Caching, filtering, pagination, and controlled refresh cycles may become just as important as the XML mapping itself.

    6. Feed Maintenance Is Often More Valuable Than One-Time Development

    External platforms change their requirements.

    Websites change their data structure.

    Hosting environments change.

    New property sources are added.

    New portals are introduced.

    A feed that worked perfectly when created may require maintenance months or years later.

    Conclusion

    This project is a good example of how a seemingly small WordPress XML-feed request can evolve into a much broader data-integration system.

    What started as a request to fix several fields in a WP All Export template eventually involved custom XML, JSON, and CSV feeds; complex property-type mapping; Thai land-measurement conversion; multilingual data; virtual tours; image handling; filtering; pagination; caching; PHP compatibility; external-platform validation; and long-term maintenance.

    The central lesson is simple:

    A successful real estate feed is not just an XML document. It is a data-transformation layer between the property’s source database and the unique requirements of every destination platform.

    When that transformation layer is designed carefully, the same WordPress property database can support many different portals and marketing channels without requiring the property data to be manually recreated for every platform.

  • Case Study 9: Building and Optimizing RSS Mashups Across 52 WordPress Websites

    Introduction

    Managing content across dozens of WordPress websites can create a significant challenge when the goal is to aggregate the latest articles into centralized RSS feeds.

    In this project, the client was managing a network of 52 WordPress websites where articles were published using WordPress Pages rather than the traditional Posts system. The requirement was to create multiple RSS mashups, with each mashup combining content from a selected group of websites into a single feed.

    The project eventually evolved beyond simple RSS aggregation to include responsive widgets, featured images, publication names, scheduled feed updates, performance optimization, duplicate-story handling, and larger content archives.

    The Initial Requirement

    The client initially wanted six RSS mashups, with each feed aggregating approximately 13 websites. Whenever one of the websites published a new article, it needed to appear automatically in the appropriate RSS mashup.

    A key technical consideration was that these websites were publishing articles through Pages instead of Posts. This meant the solution needed to work with the client’s existing publishing structure rather than assuming a conventional WordPress blog setup.

    The first mashup was eventually defined around seven websites:

    • Tarragindi News
    • Forest Lake News
    • Holland Park News
    • Sunnybank Hills News
    • Moorooka News
    • Annerley News
    • Robertson News

    The first implementation was offered as a custom WordPress plugin capable of generating an RSS mashup from those websites.

    Adding a Front-End RSS Widget

    The client did not only want an RSS feed URL. They also wanted the aggregated stories to appear directly on their websites.

    The requirement was for a widget that could display headlines from multiple publications, with the publication name shown alongside or below each story.

    The widget was therefore developed alongside the RSS mashup. The implementation was also designed to be responsive, allowing it to adapt to different device sizes.

    An option was also added to control the number of stories displayed. This allowed the client to use different limits depending on where the widget was placed—for example, displaying the latest 10 stories in one location and more stories elsewhere.

    The completed widget was subsequently installed across the seven websites in the first mashup.

    Expanding the RSS Network

    After successfully implementing the first mashup, the project expanded.

    The client began requesting additional mashups containing different numbers of websites. A pricing model based on the number of websites in each mashup was established, making it possible to scale the solution across the client’s growing network.

    The project eventually included multiple groups of websites, with separate custom plugins used for different mashups.

    This demonstrated an important advantage of the approach: rather than manually copying articles between websites, each WordPress installation could continue publishing independently while the mashup system aggregated the content automatically.

    Adding Featured Images

    As the RSS mashups became more useful, the client wanted the feeds to contain richer content.

    One requested improvement was the ability to include the featured image thumbnail associated with each article, together with the publication URL.

    The requirement was confirmed as technically possible, allowing the mashups to provide more than just text headlines.

    This made the aggregated content more suitable for visual widgets and homepage displays.

    A Separate Centralized Graphic Widget

    The project also introduced another interesting requirement.

    The client wanted a widget that could display a graphic or GIF across multiple WordPress websites. Instead of uploading the same graphic separately to every website, the idea was to maintain the graphic at a central location and have the embedded widgets display it across the network.

    The proposed approach was to use a fixed image location and consistent filename, allowing the same embedded widget to display the updated image across multiple websites.

    Although the client later found a workaround for this particular requirement, the discussion showed how the RSS project was evolving into a broader content-distribution system.

    Performance Problem: Excessive Requests

    As more mashups and websites were added, a performance issue eventually appeared.

    In May 2024, the client reported that the plugins were generating a large number of requests, sometimes more than one request per second, resulting in increased CPU usage on the server.

    This was an important turning point in the project.

    The original approach was checking for new content very frequently. While frequent checking can make feeds appear more up to date, it can become inefficient when multiple websites and mashups are involved.

    The client suggested reducing the checking frequency to approximately once per hour.

    The plugins were subsequently updated so that the feed refresh frequency was reduced, helping minimize unnecessary server requests.

    Updates were supplied for multiple groups of websites, including seven-site, five-site, six-site, and ten-site installations.

    Solving a “Too Many Requests” Feed Problem

    The performance improvements became particularly relevant when one of the mashup feeds later developed problems.

    In May 2025, the client reported that the West Brisbane News Feed had broken links, while another feed was displaying errors.

    After investigation, the West Brisbane issue was identified as being related to “Too many requests.” The feed was changed to update approximately once per hour instead of making requests continuously.

    A temporary alternative feed was also provided while the updated system took effect.

    The plugin was then further optimized to reduce server load.

    This part of the project highlighted an important lesson in feed development:

    A feed aggregator needs to balance freshness with server efficiency.

    Checking for new content every second is usually unnecessary for news aggregation and can create significant server load when the system scales across many websites.

    Scaling to Larger Mashups

    By 2025, the client was requesting even larger mashups.

    New requirements included mashups combining 10 and 13 websites, while the client also had potential future mashups containing 16 and 26 websites.

    The project had therefore grown considerably from its original seven-site RSS feed.

    The client also wanted to retain the established format, including:

    • A defined number of stories
    • Publication name instead of author name
    • Hourly refresh
    • Potentially displaying story dates
    • Installation across multiple WordPress websites

    This required the RSS mashup system to remain flexible as the number of source websites increased.

    Handling Duplicate Stories

    Another challenge appeared as the client began publishing some stories across multiple publications.

    Because the same article could appear on several websites, the RSS mashup could potentially display what appeared to be duplicate stories.

    In July 2025, the client asked whether the system could be improved so that only one version of an article would appear in the mashup when the same story had been published across multiple sites.

    A title-based comparison approach was proposed for identifying duplicates.

    The updated plugin would be installed across the WordPress websites participating in the mashup.

    This represented another step forward—from simply aggregating content to intelligently controlling how aggregated content was presented.

    Improving Mobile Presentation

    The client also wanted the RSS widget to look better on the homepage, particularly on mobile devices.

    The proposed improvement involved responsive CSS so that images could occupy the full available width on mobile screens.

    This was important because the same RSS content was being displayed in different layouts and devices.

    The project therefore required consideration of both:

    • Backend feed generation
    • Frontend content presentation

    Archive and Content Volume Requirements

    As the amount of aggregated content increased, the client wanted to use the mashup as an archive as well as a live news display.

    In July 2025, the client asked whether pagination could be added to the archive. When pagination was determined not to be possible within the existing setup, the alternative was to increase the number of displayed items for the main homepage while retaining a smaller number for the sidebar.

    The number of displayed items was subsequently increased.

    This was another example of adapting the implementation to the practical requirements of the existing WordPress environment rather than rebuilding the entire system.

    Project Evolution

    What started as a request for six RSS mashups eventually became a long-term WordPress feed development and maintenance project.

    The major stages included:

    1. Initial RSS mashup development
    2. Aggregation of WordPress Pages from multiple websites
    3. Responsive RSS widgets
    4. Configurable article limits
    5. Featured image support
    6. Multiple independent mashups
    7. Feed refresh optimization
    8. CPU/server-load reduction
    9. Troubleshooting “Too many requests” issues
    10. Larger 10-, 13-, 16- and 26-site mashups
    11. Duplicate-story detection
    12. Mobile layout improvements
    13. Larger content displays for archive-style usage

    Key Technical Lessons

    1. Aggregation becomes more complex as the network grows

    A feed that works well with a few websites can behave very differently when dozens of websites are involved.

    Request frequency, caching, server resources and feed size become increasingly important.

    2. Real-time does not always mean every-second polling

    For a news aggregation system, hourly updates may provide an appropriate balance between freshness and server performance. In this project, excessive request frequency eventually contributed to CPU and “Too many requests” problems.

    3. RSS feeds can become part of the website’s front-end

    The project demonstrated that RSS does not have to be used only as a backend data format. The aggregated feed can also power custom widgets and homepage content displays.

    4. Duplicate content needs to be considered

    When the same publisher operates multiple websites, the same story may legitimately appear on several domains. A title-based comparison can help reduce repeated stories within an aggregated feed.

    5. Mobile presentation matters

    An RSS feed may technically work while its visual presentation remains poor. Responsive CSS and appropriate image sizing can significantly improve how aggregated content appears on phones and other devices.

    Conclusion

    This case demonstrates how a relatively simple RSS requirement can evolve into a sophisticated multi-site content aggregation system.

    The original requirement was to combine articles from a network of WordPress websites into several RSS mashups. Over time, the system expanded to support widgets, images, configurable story limits, larger website groups, scheduled updates, performance optimization, duplicate detection and improved mobile presentation.

    The most valuable aspect of the project was not simply creating an RSS feed—it was continuously adapting the feed infrastructure as the client’s network, publishing strategy and technical requirements changed.

    For organizations managing multiple WordPress websites, a custom RSS/XML aggregation solution can provide a practical way to centralize content while allowing each individual publication to continue operating independently.

  • Case Study 7: Building and Maintaining Custom RSS Feeds for Yahoo, MSN and Multi-Site Content Syndication

    Introduction

    Content syndication can be deceptively complex. A WordPress website may have a perfectly valid RSS feed, yet that feed may not work correctly with a major publishing or syndication platform because of differences in formatting, links, dates, embedded media, content length, caching, or platform-specific requirements.

    This case study follows a long-term RSS feed development and maintenance project for a publisher operating multiple automotive and news websites. What began as a request to customize an existing RSS feed eventually developed into an ongoing technical partnership covering Yahoo and MSN-compatible feeds, multiple websites, media handling, feed filtering, troubleshooting, and WordPress maintenance.

    The project demonstrates why a successful syndication feed requires more than simply generating valid XML.

    The Initial Requirement

    The first conversation began in December 2022 when the client asked about creating an RSS feed for The Auto Wire, along with unique feeds for Yahoo and MSN.

    The website already had a standard WordPress RSS feed:

    https://theautowire.com/feed

    The first step was therefore not to create an entirely new system unnecessarily, but to understand the existing feed and determine what format the syndication partners required.

    The project became active again in August 2023 when the client supplied Yahoo’s technical guidelines for article ingestion and explained that many articles were not being pulled correctly from the site’s news section.

    A custom WordPress feed update was then commissioned.

    Adapting the Existing RSS Feed to Yahoo’s Requirements

    The initial task was relatively small: modify the existing RSS feed according to Yahoo’s technical specifications.

    The custom implementation was offered as an RSS/XML feed project, with the objective of updating the existing feed rather than replacing it unnecessarily.

    However, once Yahoo began ingesting the content, several practical issues appeared.

    The client reported that some articles were appearing as block text and that article links were missing. Importantly, the client preferred not to submit an entirely new feed because doing so could potentially introduce another approval delay.

    The solution was to modify the original feed so that it contained properly formatted content and links while retaining the existing feed URL.

    This was an important lesson from the project:

    When a syndication feed is already approved or being processed, improving the existing feed can sometimes be preferable to replacing it with a completely new feed.

    Correcting Publication Dates

    Another problem appeared with article timestamps.

    The client noticed that an article published on the website that day was appearing in Yahoo as though it had been published two days earlier.

    Investigation revealed that the feed was using the post-modified date rather than the original publication date.

    The feed was updated to use the post publish date, which aligned the syndication information more closely with when the article was actually published.

    For news websites, this distinction is particularly important because syndication platforms may use timestamps to determine article freshness and ordering.

    Handling Embedded Videos and Tweets

    The next challenge involved embedded media.

    The client noticed that embedded videos and tweets were appearing as raw URLs on Yahoo instead of being rendered as intended. The concern was that the site’s embedded content was being corrupted or transformed during RSS generation.

    The feed was subsequently updated to preserve the content being supplied to the syndication platform, and the client was asked to allow the syndication system to perform another fetch.

    This illustrates another important point about RSS development:

    A feed is not simply a text export of a webpage.

    HTML, JavaScript-generated embeds, video players, social posts, images and other media can behave very differently when consumed by an external platform.

    Expanding the Solution to a Second Website

    The successful work on The Auto Wire led to another project.

    In September 2023, the client requested a new feed for Backfire News, following the same Yahoo technical guidelines.

    A custom WordPress plugin/feed implementation was developed for the second site.

    The client later confirmed that the syndication feed had been published on Yahoo and that everything looked good, with only a small wording adjustment required in the “Read the full story” section.

    At this stage, the project had evolved from a one-off RSS customization into a reusable approach for multiple publishing websites.

    Troubleshooting Feed Links

    In November 2023, a major feed issue appeared.

    The client reported that links in the RSS feed were pointing to images rather than the actual articles. The problem affected syndicated content and required immediate investigation.

    After checking the feed, the links were confirmed to be functioning correctly again.

    This type of issue demonstrates why feed troubleshooting should include testing the actual generated XML and destination URLs, rather than relying solely on how the WordPress page appears in a browser.

    Adding Newsletter and Social Media Information

    In February 2024, the client requested another enhancement.

    The RSS feeds needed a standard footer containing newsletter and social media information. The requirement applied to both The Auto Wire and Backfire News, with different wording and links for each website.

    The implementation was extended so social links could be added to the bottom of syndicated content, alongside the existing “Read the full story” information.

    The same approach was subsequently applied to a new website, Modern Car Collector, which also required a feed based on updated Yahoo article-ingestion guidelines.

    Supporting a Third Website

    Modern Car Collector became the third site in the feed ecosystem.

    After the feed was delivered, the client submitted it to the syndication partner for review. A temporary site-access issue was also reported during the process, and the website was checked from another environment.

    The client then requested social links to be added to the new feed, including Facebook and Twitter. These were added shortly afterward.

    The same type of customization was then applied to The Auto Wire’s feed with its own newsletter and social wording.

    Diagnosing Delayed Feed Ingestion

    One of the more technically interesting problems appeared in February 2024.

    The client reported that posts from Modern Car Collector and Backfire News were not appearing in the RSS feeds immediately after publication. The feeds were also being checked using evaluation tools associated with the syndication process.

    Initially, the issue was investigated from the feed and WordPress side. Time-zone settings were checked and confirmed to be correct.

    Further investigation led to caching being considered as a potential source of delay. The client was asked to provide hosting access or contact the hosting provider to disable caching for the feed URL. Changes were then applied to the feeds.

    This was a valuable distinction:

    When a WordPress post is published but an external feed still shows old content, the problem may not be the feed-generation code itself.

    Caching at the WordPress, plugin, server, CDN, or hosting level can cause an otherwise correctly generated feed to appear stale.

    MSN Feed Development and YouTube Content

    Later in 2024, the project expanded beyond article RSS feeds.

    The client wanted a feed for The Auto Wire’s YouTube videos that could work with MSN’s media requirements. The client supplied detailed Media RSS specifications describing how images, videos and other media should be represented using elements such as media:content and media:group.
    This introduced a different technical problem from traditional article RSS generation.

    The feed now needed to deal with:

    • YouTube content
    • Video metadata
    • Media RSS elements
    • External API access
    • Syndication requirements
    • Content validation

    Solving YouTube API Quota Problems

    Soon after implementation, a video failed to populate in the feed.

    Investigation identified the cause as YouTube API quota limits being exceeded. A new API key was created and monitoring was put in place.

    This was an important reminder that integrations with external APIs introduce dependencies outside the WordPress code itself.

    Even when the feed-generation logic is functioning correctly, an API quota, authentication problem, rate limit or external service failure can prevent new content from entering the feed.

    Meeting Minimum Content-Length Requirements

    Another MSN-related issue appeared when the syndication system rejected content because articles needed to contain at least 450 characters.

    The plugin was updated to handle the requirement, and subsequent testing showed that feed items contained substantially more content.

    However, the client later noticed that only part of the description appeared in the syndicated result.

    The feed was adjusted so the full description could be provided, and subsequent MSN examples showed the video content being displayed successfully.

    This part of the project demonstrates the iterative nature of syndication development:

    1. Generate the feed.
    2. Validate the XML.
    3. Submit it to the syndication platform.
    4. Observe how the platform interprets it.
    5. Identify validation or rendering issues.
    6. Adjust the feed.
    7. Test again.

    Creating a Separate Feed for MSN

    In January 2025, the client reported that The Auto Wire’s existing feed worked well with Yahoo but had issues with MSN.

    Instead of changing the existing Yahoo feed and potentially affecting its behavior, the client asked for a duplicate feed specifically for MSN.

    During investigation, an image-related problem was identified in one of the posts. The image filename needed correction, but the WordPress post could not be saved because of a permissions/security restriction.

    A separate feed was subsequently commissioned.

    This approach provided an important architectural advantage:

    One website can have different feeds for different syndication partners.

    Instead of forcing Yahoo and MSN to consume exactly the same output, separate feeds can be tailored to the technical requirements of each platform.

    Adding Per-Post Feed Filtering

    The client later requested more control over which articles appeared in the new MSN feed.

    The requirement was specific:

    • Certain posts should be excluded from the new feed.
    • Those same posts should remain available in the original RSS feed.
    • The site editor needed an easy way to control this from WordPress.

    The solution was to add a checkbox option to individual WordPress posts.

    This transformed the feed from a purely automatic system into a system with editorial control.

    Instead of manually editing XML or deleting posts, the publisher could decide which content belonged in the specialized feed while leaving the main RSS feed untouched.

    Handling YouTube Embeds in MSN Feeds

    Another issue involved YouTube videos appearing as raw URLs in syndicated content.

    The client reported that MSN’s moderation tool was detecting the video URLs rather than receiving the expected embedded video representation.

    Investigation showed that the webpage’s iframe was being generated after page load using JavaScript, meaning the iframe was not necessarily present in the raw content available to the RSS generator.

    A proposed solution was to detect YouTube URLs and generate iframe markup directly in the RSS feed.

    The client temporarily paused that change while clarifying the syndication partner’s requirements.

    This highlighted an important technical concept:

    What a browser renders is not necessarily what an RSS parser receives.

    A JavaScript-generated embed may look perfect on the website while appearing only as a plain URL to an external feed consumer.

    WordPress and Server-Level Troubleshooting

    The relationship also expanded beyond RSS development.

    In March 2025, the client encountered a PHP warning related to the RSS plugin and subsequently received a 500 Internal Server Error.

    The issue appeared to involve the hosting/server environment rather than simply the feed output.

    The client provided hosting access for investigation. By the time access was obtained, the website was functioning again, and the issue was considered consistent with a temporary server update/glitch.

    This is another common reality of long-term WordPress projects: once a custom plugin becomes critical to a publishing workflow, maintenance may include troubleshooting the interaction between WordPress, PHP, plugins, hosting and server updates.

    Further Feed Customization

    In August 2025, the client returned with another request affecting all three RSS feeds.

    This time, Yahoo needed the “Read the full story on…” text removed. A single customization was applied across the three feeds.

    By this point, the project had developed into an ongoing maintenance relationship rather than a one-time feed-generation job.

    What Made This Project Challenging?

    The technical challenge was not simply generating XML.

    The project involved multiple layers:

    1. WordPress content extraction

    The system had to correctly identify posts, publication dates, descriptions, links and media from WordPress.

    2. Custom XML/RSS formatting

    The standard WordPress RSS structure was insufficient for the requirements of external syndication platforms.

    3. Platform-specific requirements

    Yahoo and MSN had different expectations regarding article content, media, formatting and validation.

    4. External APIs

    The YouTube integration introduced API quotas and external-service dependencies.

    5. Media handling

    Images, videos, iframes, social embeds and raw URLs required special consideration.

    6. Caching

    Feed caching could cause delays between publication and syndication.

    7. Editorial control

    The publisher eventually needed the ability to exclude individual articles from one feed while keeping them in another.

    8. Hosting and server issues

    Some problems occurred outside the feed-generation logic and required investigation at the WordPress or hosting level.

    The Result

    Over the course of the project, the work expanded from one RSS feed to a multi-site syndication system supporting several publishing properties.

    The work included:

    • Custom Yahoo-compatible RSS feeds
    • MSN-specific RSS feed development
    • Multiple website feeds
    • Publication-date corrections
    • Formatted article content
    • Article links
    • Newsletter and social media footers
    • Media RSS requirements
    • YouTube video feed integration
    • API quota troubleshooting
    • Content-length validation
    • Full-description handling
    • Separate feeds for different syndication partners
    • Per-post feed exclusion controls
    • Video/embed troubleshooting
    • Feed caching investigation
    • WordPress/PHP troubleshooting
    • Ongoing feed maintenance

    The client repeatedly returned with new requirements and additional websites, eventually describing the work as part of a broader need for WordPress assistance across the sites.

    Key Lessons from the Project

    A valid RSS feed is not necessarily a syndication-ready RSS feed.

    XML can be technically valid while still failing the requirements of a specific publishing platform.

    Preserve existing feeds when appropriate.

    If a feed is already being used or approved by a syndication partner, modifying the existing feed can sometimes be safer than replacing it.

    Always test real-world ingestion.

    A feed can look correct in an XML viewer while the receiving platform interprets its content differently.

    Publication dates matter.

    Using the wrong WordPress date field can make newly published articles appear old to a syndication platform.

    External dependencies need monitoring.

    YouTube API quotas demonstrated that feed reliability can depend on services outside WordPress.

    Separate feeds can solve conflicting requirements.

    Yahoo and MSN did not necessarily need identical output. Dedicated feeds allowed the same website to provide different content structures for different partners.

    Editorial controls can make automated feeds more practical.

    A simple per-post checkbox gave the publisher control without requiring manual XML editing.

    Feed maintenance is an ongoing process.

    Syndication platforms change requirements, websites change, plugins change, hosting environments change, and content formats evolve. A feed that works today may require adjustments later.

    Conclusion

    This project began with a simple request to customize an existing WordPress RSS feed but evolved into a multi-year feed development and maintenance relationship.

    The biggest takeaway is that RSS feed development for professional content syndication is an integration problem, not merely an XML-generation problem.

    A reliable solution must consider WordPress data, XML structure, publication dates, links, media, APIs, caching, validation tools, syndication requirements and the way external platforms actually consume the feed.

    For publishers relying on Yahoo, MSN or other content-distribution platforms, having a properly engineered and maintainable feed can be just as important as having a well-functioning website.

  • Case Study 5: XML Job Feed and Predictable Vacancy URLs for RecruitNow

    Category: XML Feed Development
    Industry: Recruitment / Job Listings
    Platform: WordPress
    Integration: RecruitNow / Indeed
    Project Type: Custom XML Feed & Vacancy URL Architecture

    Project Overview

    A recruitment website needed a way to provide its job vacancies through an XML feed while also giving each vacancy a predictable URL based on a unique vacancy ID.

    The requirement was intended to support integration with RecruitNow and job boards such as Indeed, where a predictable vacancy URL could be generated automatically rather than relying on the existing job title-based URL.

    The project involved two connected requirements:

    1. Create a custom XML feed containing vacancy information and a unique vacancy ID.
    2. Create a predictable URL structure using that same ID and redirect it to the actual vacancy page.

    For example:

    https://baantjeuitzendbureau.nl/vacatures/12345

    would redirect to the actual vacancy page:

    https://baantjeuitzendbureau.nl/vacatures/orderpicker-logistiek-medewerker/

    The key idea was to use the same unique identifier in both the XML feed and the redirect URL.

    The Challenge

    The website’s existing vacancy URLs were based primarily on job titles.

    For example:

    /vacatures/orderpicker-logistiek-medewerker/

    The client explained that Indeed required a predictable URL structure containing a vacancy ID. The existing URLs did not provide that ID in a predictable position.

    This created a problem for the external feed integration.

    A job portal should be able to receive a vacancy ID from the XML feed and construct a URL without needing to know the actual title or permalink of the vacancy.

    The proposed structure was:

    /vacatures/{vacancyId}

    For example:

    /vacatures/12345

    The system would then identify the vacancy associated with 12345 and redirect the visitor to the actual vacancy page.

    The client specifically requested this type of URL-and-redirect behavior.

    The Proposed Solution

    The proposed architecture connected the XML feed and redirect system through a common vacancy ID.

    Step 1 — Identify the Vacancy ID

    Each vacancy would have a unique identifier.

    For example:

    vacancyId = 12345

    This ID would become the stable reference for the vacancy.

    Step 2 — Include the ID in the XML Feed

    The XML feed would expose the vacancy ID together with the vacancy information.

    A simplified feed item could look like:

    <vacancy>
    <vacancyId>12345</vacancyId>
    <title>Orderpicker Logistiek Medewerker</title>
    <detailUrl>
        https://baantjeuitzendbureau.nl/vacatures/orderpicker-logistiek-medewerker/
    </detailUrl>
</vacancy>

    The important part is that vacancyId remains consistent with the identifier used by the redirect URL.

    The original project discussion also specified that the same ID should be available in the XML feed so RecruitNow could construct the predictable URL.

    Step 3 — Create the Predictable Vacancy URL

    A separate URL pattern would be made available:

    https://baantjeuitzendbureau.nl/vacatures/{vacancyId}

    For example:

    https://baantjeuitzendbureau.nl/vacatures/12345

    This URL does not contain the job title.

    That makes it predictable and suitable for an external system to construct automatically.

    Step 4 — Redirect to the Actual Vacancy

    When someone visits:

    /vacatures/12345

    the WordPress implementation would:

    1. Extract 12345 from the URL.
    2. Find the corresponding vacancy.
    3. Determine its actual permalink.
    4. Redirect the visitor to that page.

    Conceptually:

    /vacatures/12345
        ↓
Find vacancy ID 12345
        ↓
Find actual vacancy URL
        ↓
/vacatures/orderpicker-logistiek-medewerker/

    This separates the stable external identifier from the changeable public vacancy URL.

    Why This Architecture Is Useful

    Job titles can change.

    For example, a vacancy might initially be published as:

    /vacatures/orderpicker/

    and later become:

    /vacatures/orderpicker-logistiek-medewerker/

    If an external platform depends directly on the title-based URL, such changes can create broken links or require the external feed configuration to be updated.

    A vacancy ID provides a more stable reference:

    /vacatures/12345

    The actual destination can change internally while the external URL remains predictable.

    This is particularly useful when a third-party recruitment platform needs to construct vacancy URLs automatically.

    XML Feed + Redirect Architecture

    The complete concept can be represented as:

                     WordPress Vacancy
                        │
                        ▼
                Unique Vacancy ID
                     12345
                        │
             ┌──────────┴──────────┐
             ▼                     ▼
        XML Job Feed        Predictable URL
        vacancyId=12345     /vacatures/12345
             │                     │
             ▼                     ▼
        RecruitNow /          WordPress
           Indeed             Redirect
                                   │
                                   ▼
                         Actual Vacancy Page

    The XML feed and redirect mechanism therefore use the same identifier as the connection point.

    Initial Project Scope

    The original custom offer covered the setup of the XML feed and redirect URL functionality for RecruitNow. The offer included XML feed creation and redirect URL setup.

    During the discussion, the client confirmed that the XML feed needed to contain vacancy information and that the redirect should work using a unique ID.

    However, before implementation could be completed, the client explained that their original brief had been based on the wrong solution.

    The order was subsequently canceled while the client clarified the revised requirement.

    The client later returned with a more specific requirement: create an additional URL ending in the vacancy ID and redirect that URL to the actual vacancy detail page.

    Project Status

    This case study represents the technical analysis and proposed implementation approach, rather than a completed production deployment.

    The original order was canceled before the implementation was completed because the client’s requirements changed.

    That distinction is important: the case study demonstrates the technical problem, architecture, and proposed solution without claiming that the final system was successfully deployed.

    Key Takeaways

    This project demonstrates an important principle when building XML feeds for third-party job platforms:

    The feed and the destination URL should have a reliable common identifier.

    Instead of depending entirely on a changing job title or permalink, a unique vacancy ID can provide a stable reference between:

    • WordPress vacancy records
    • XML feed items
    • RecruitNow
    • Indeed
    • Predictable external URLs
    • Internal redirects

    A well-designed integration can therefore look like:

    WordPress
   ↓
Vacancy ID
   ├── XML Feed
   └── Predictable URL
          ↓
      Redirect
          ↓
Actual Vacancy Page

    For recruitment websites integrating with external job platforms, this approach can make the feed and URL architecture more predictable, maintainable, and easier for third-party systems to consume.

    Need a Custom XML Job Feed?

    If your WordPress website needs a custom XML, RSS, or job feed for a recruitment portal, job board, ATS, or third-party platform, the feed can be mapped to your existing WordPress vacancy structure and the required external format.

  • Case Study 4: Rebuilding and Troubleshooting a Real Estate & Boat XML Feed After a Domain Migration

    From a Simple “Add Brand” Request to Reliable Marketplace Feed Integration

    Project Overview

    A Danish boat-sales business was migrating from its old domain, dansksejlogmotor.dk, to a new branded domain, ditbaadsalg.dk.

    The domain migration itself was straightforward, but it created an important technical problem: the business relied on XML feeds to distribute its boat listings to external marketplaces, including DBA.dk and ScanBoat.

    After the migration, the feeds were still referencing the old domain and several pieces of structured listing data were not being transferred or displayed correctly.

    What initially started as a small request to add a brand field eventually became a broader XML feed debugging and optimization project involving:

    • Domain migration
    • XML field mapping
    • Product/boat specifications
    • Category mapping
    • Description formatting
    • Image ordering
    • Sold/out-of-stock filtering
    • Price synchronization
    • Scheduled feed updates
    • DBA validation
    • ScanBoat validation
    • Comparison with the previously working feed

    The project demonstrates an important principle in XML feed development: generating valid XML is only one part of the job. The receiving marketplace must also interpret every field correctly.

    1. The Initial Problem

    The business had migrated from:

    dansksejlogmotor.dk

    to:

    ditbaadsalg.dk

    The existing DBA and ScanBoat feeds were still containing URLs from the old domain.

    The first request was therefore to update the feeds so they would work with the new domain.

    Shortly afterward, the client identified another requirement:

    The DBA feed also needed to include the boat’s brand value.

    The client explained that the brand was already entered on the website, but the value was not being included in the XML output.

    At this stage, the task appeared to be a relatively small XML modification.

    2. Adding the Brand Field Exposed Other Feed Problems

    After the brand field was added, the client noticed that some boat descriptions were no longer appearing correctly in the feed.

    For example, the description for a boat such as Saga 26 HT appeared correctly on the website but was being displayed incorrectly in the feed.

    Investigation showed that the existing function responsible for cleaning descriptions for XML output was not working correctly.

    A new description-cleaning approach was therefore required.

    At the same time, another issue appeared: images were being selected in the wrong order.

    Instead of:

    1. Main image
    2. Second image
    3. Third image
    4. etc.

    the feed could contain images in an unexpected order.

    The client specifically requested that the primary product image should always be the first image.

    3. Fixing Image Ordering

    The image logic was updated so that the featured image was placed first in the XML media output.

    The change was subsequently applied to both the DBA and ScanBoat feeds.

    This was important because marketplace feeds are not simply data exports. The order and structure of repeated elements can affect how the receiving platform displays a listing.

    The client later confirmed that the image issue had been resolved.

    4. Sold Listings Were Still Appearing

    Another issue then surfaced.

    The client found several boats that had already been sold—or were hidden drafts—still appearing in the feed.

    The affected listings included:

    • Awi 23
    • Svensk træbåd
    • Princess 415
    • Monterey 254
    • Coaster 600 DC
    • Cranchi Smeraldo

    The website already had a condition intended to exclude products where _stock_status was outofstock.

    This required checking the relationship between the WordPress/WooCommerce product status and the actual feed-generation logic.

    This illustrates another common XML-feed problem: the website can display a listing correctly while the feed-generation rules use different conditions.

    5. Marketplace-Specific Field Mapping

    Once the basic feed issues were addressed, DBA began reporting problems with structured fields.

    Some important information was appearing as:

    • Length: Not specified
    • Engine type: Not specified
    • Seats: Not specified
    • Type: Other

    The client requested that the feed correctly map the boat information to DBA’s expected fields.

    The investigation then moved beyond simply producing XML.

    The receiving platform’s expected field names, formats and category structure became part of the debugging process.

    The client also supplied the old feed as a reference because it had previously worked correctly.

    This provided a valuable baseline:

    Old working feed → New feed → Side-by-side comparison

    6. Reproducing the Old Working Feed

    A particularly important requirement emerged during the project.

    The client wanted the new feed to be as close as possible to the previously working feed from the old domain, while adding the new brand field.

    The requested approach was essentially:

    Make the new feed identical to the old feed, change the sender/domain, add the required fields, and preserve the existing formats.

    The requested structured fields included:

    • category_id
    • engine_included
    • engine_type
    • engine_brand
    • engine_power_hp
    • fuel_type
    • length_feet

    along with the previously added brand field.

    The updated feed was then regenerated with these additional fields.

    7. Category Mapping Became a Critical Issue

    One of the more interesting problems was the DBA category.

    At one point, the client discovered that a value such as:

    <category>37000</category>

    was appearing in the feed and suspected that this was responsible for the incorrect marketplace display.

    The discussion then moved toward whether DBA expected a category value or a category_id value.

    A change to category_id was tested, but DBA subsequently indicated that the system was undergoing a migration to its new Dealer Hub system. The category mapping therefore could not be treated as an isolated XML problem—the receiving platform’s import system was also changing.

    The category change was eventually reverted as requested.

    Lesson

    When troubleshooting marketplace feeds, it is important to distinguish between:

    Feed-side problems

    and

    Marketplace-side import problems.

    A perfectly generated XML feed can still display incorrectly if the marketplace has not reprocessed it, is changing its import system, or is interpreting a field differently.

    8. Feed Updates Were Not Happening Quickly Enough

    Later in the project, the client noticed that:

    • A boat with a new price was still showing its old price in the marketplace.
    • A sold boat was still appearing in the marketplace.

    The client suspected that the feeds were not updating.

    The feed itself needed a more reliable update mechanism.

    A cron job was added so the feed would be refreshed every five minutes.

    This was an important improvement because there are actually two separate stages:

    WordPress data → XML feed → Marketplace import

    Updating the XML feed does not necessarily mean the marketplace has immediately imported the new data.

    That distinction became particularly important during DBA testing.

    9. DBA and ScanBoat Required Different Validation

    The project involved two external platforms:

    • DBA
    • ScanBoat

    Even though both consumed XML feeds, their expectations and processing behavior were not necessarily identical.

    The client reported that ScanBoat was receiving correct information from the old feed but not from the new feed.

    The requirement was to make the new ScanBoat feed reproduce the same data and formatting as the old feed, including decimal formatting.

    The ScanBoat feed therefore required its own validation rather than assuming that fixing the DBA feed would automatically solve the ScanBoat integration.

    10. Description Formatting

    After the marketplace began receiving the updated data, another presentation issue became visible.

    The boat description and technical specifications were appearing as one continuous block of text.

    The client wanted the content separated into readable sections such as:

    Description

    The boat’s main description.

    Dimensions

    • Feet
    • Length
    • Width
    • Draft
    • Displacement
    • Hull type
    • Berths

    Mechanical

    • Engine
    • Batteries
    • Shore power

    Equipment

    • Cockpit equipment
    • Cabin equipment
    • Refrigerator
    • Toilet
    • Other accessories

    The feed output was adjusted so the information would appear with improved separation and readability.

    The client subsequently confirmed that the text had been separated in both feeds.

    11. Testing the Feed Against Real Listings

    Rather than relying only on XML inspection, the project involved checking actual listings across the website and the marketplace.

    For example, a specific boat was compared between:

    Website listing → XML feed → DBA listing

    The client supplied actual listing URLs when an inconsistency appeared, allowing the feed data to be compared with what DBA was displaying.

    This approach is especially important for marketplace integrations.

    A feed can be:

    • syntactically valid,
    • accessible,
    • correctly formatted,

    and still produce an incorrect listing because the receiving platform interprets a field differently.

    12. The Final Testing Stage

    Toward the end of the project, the client reported that ScanBoat was working correctly.

    DBA was also displaying the listings more accurately, although additional marketplace-side processing and testing remained necessary.

    The final testing included new boat listings as well as existing/used boats.

    The project also involved checking whether length in feet was being transmitted correctly. The feed contained the length_feet field, while the client continued checking the behavior on DBA’s side.

    The client eventually confirmed on December 2, 2025:

    “Job is done :-)”

    Technical Challenges Solved

    The project ultimately addressed a much broader set of requirements than the original brand request.

    AreaIssueSolution / Approach
    Domain migrationOld domain URLs remained in feedsUpdated feed output for the new domain
    BrandBrand existed in WordPress but was missing from XMLAdded brand mapping
    DescriptionText was incorrectly formattedUpdated XML-safe description processing
    ImagesPrimary image was not consistently firstFeatured image moved to first position
    Sold listingsOut-of-stock items appeared in feedsChecked feed filtering conditions
    CategoryMarketplace category was interpreted incorrectlyCompared category/category ID requirements
    Boat specificationsLength, engine and other fields missingAdded and mapped structured fields
    PriceUpdated prices were not immediately visibleVerified feed output and marketplace reprocessing
    Feed freshnessChanges were not reflected quicklyAdded a five-minute cron refresh
    ScanBoatNew feed differed from old working feedCompared and adjusted output
    FormattingDescription/specifications appeared as one blockImproved output separation
    ValidationFeed output and marketplace display differedTested actual listings end-to-end

    The Most Important Lesson

    This project demonstrates why XML feed development is more than generating XML syntax.

    A successful marketplace feed has at least four layers:

    1. Source data

    WordPress custom fields, product data, images, prices and status.

    ↓

    2. Feed mapping

    Correct XML tags, values, data types, formatting and filtering.

    ↓

    3. Feed delivery

    A stable, accessible and regularly updated XML endpoint.

    ↓

    4. Marketplace interpretation

    DBA, ScanBoat or another portal imports and maps the feed according to its own specifications.

    A problem can occur at any of these layers.

    That is why simply opening an XML URL in a browser is not always enough to determine whether a feed integration is working correctly.

    Result

    The project evolved from a small feed customization into a complete troubleshooting and synchronization exercise.

    The final work addressed:

    • New-domain feed output
    • Additional structured fields
    • Brand mapping
    • Boat specifications
    • Image ordering
    • Description cleaning
    • Description formatting
    • Listing filtering
    • Category handling
    • Feed refresh scheduling
    • DBA testing
    • ScanBoat testing
    • Comparison with the previous working feed

    Most importantly, the project ended with the client confirming that the job was complete and expressing interest in working together again.

    What This Case Study Shows

    For businesses moving websites, changing domains, adding marketplace integrations, or replacing an existing XML feed, the safest approach is not to build the new feed from scratch without reference.

    Instead:

    1. Preserve the existing working feed structure where possible.
    2. Compare old and new feeds item by item.
    3. Map every important custom field explicitly.
    4. Treat images as structured data, not just URLs.
    5. Filter sold, hidden and unavailable listings correctly.
    6. Validate marketplace-specific categories and field formats.
    7. Understand the difference between feed generation and marketplace import.
    8. Allow for marketplace caching and scheduled imports.
    9. Test real listings from the website through the feed to the marketplace.

    This methodology can significantly reduce the risk of losing or incorrectly displaying listings after a website migration.

    Need a Custom XML Feed?

    If your WordPress website needs a custom XML, RSS or JSON feed for a real estate portal, marketplace, directory, advertising platform or another external system, the important question is not simply:

    “Can you generate XML?”

    The real question is:

    “Can the receiving platform correctly understand and use the data?”

    That is where careful field mapping, feed validation and real-world testing make the difference.

  • Spent more time writing documentation than writing code

    Spent more time writing documentation than writing code

    For the past several weeks, I’ve spent more time writing documentation than writing code.

    The development work for a WordPress XML feed project was completed early, but the project became stuck in an endless documentation and evidence cycle. Every answer generated new requests for additional screenshots, logs, timestamps, headers, test evidence, architecture notes, and acceptance clarifications.

    Documentation is important. Good documentation protects both the client and the developer. But there is a point where documentation stops supporting delivery and starts replacing it.

    One lesson I’ve learned is to define documentation boundaries before development begins:
    • What evidence will be required for acceptance?
    • How many review rounds are included?
    • What constitutes a completed deliverable?
    • When does additional documentation become a separate milestone?

    As developers, we often assume that once the software works, we’re almost finished. In reality, some projects can spend more time in review than in implementation.

    Going forward, I’ll be including documentation scope and acceptance criteria as part of every proposal. It helps keep expectations clear, protects project timelines, and ensures both sides stay focused on delivering value rather than creating endless paperwork.

    Every project teaches something. This one reinforced that good project management is just as important as good code.

    #WordPress #SoftwareDevelopment #Freelancing #XML #API #ProjectManagement #Documentation #WebDevelopment

  • How to earn money by learning XML

    That’s a great question — and a smart one, because XML (Extensible Markup Language) may sound old-fashioned, but it still powers a lot of data exchange across industries. Let’s go step by step on how you can actually earn money by learning XML — both directly and indirectly.

    💡 1. Understand What XML Is Used For

    XML is mainly used to store and share structured data between systems — websites, apps, APIs, and software platforms.
    Once you understand it deeply, you can earn by working on projects that involve:

    • Data feeds (like property listings, product catalogs, job listings, ads)
    • Software integrations (connecting one app to another)
    • Content syndication (sending or receiving structured data)
    • Custom web tools or WordPress plugins

    💼 2. Real Ways to Earn Money with XML

    (a) Freelancing / Service Work

    Offer services on platforms like Upwork, Fiverr, Freelancer:

    • Convert data between XML and CSV/JSON
    • Create XML feeds for eCommerce, real estate, or job portals
    • Modify or validate XML for integrations
    • Create WordPress/XML-related plugins or scripts

    👉 Example: “I will create an XML feed for your real estate listings website for ₹2,000”
    You can easily automate it once, and then sell repeatedly.

    (b) WordPress Plugin or Tool Development

    You already mentioned your plugin — “WordPress to XML Feed”.
    That’s a perfect XML-based business idea.
    You can:

    • Sell Pro versions (add more export options)
    • Offer custom feed setup services
    • Create affiliate program or tutorials teaching others to earn using your plugin

    (c) XML + API Integration Projects

    Many websites use XML APIs (e.g., property portals, job boards, vehicle listings).
    You can charge clients to:

    • Fetch data from external XML APIs and display it on their sites
    • Push their site data to third-party services using XML feeds

    💰 These projects can earn ₹5,000–₹50,000 depending on complexity.

    (d) Teach XML or Create Courses

    If you understand XML and WordPress integration, you can:

    • Create a YouTube channel (“XML for WordPress Developers”)
    • Write an eBook or blog (“How to create XML feeds for real estate websites”)
    • Sell courses on Udemy, Skillshare, or Gumroad

    (e) Data Management or Tech Jobs

    XML is still common in:

    • Banking and finance systems (data exchange)
    • Government data services
    • Medical and publishing industries (standardized data formats)

    Roles like:

    • Data integration specialist
    • API developer
    • XML/XSLT engineer
      often pay ₹6–15 LPA (in India) or $60k+ abroad.

    🧠 3. What to Learn Next

    To really earn from XML, combine it with these:

    SkillWhy
    XSLT / XPathFor transforming and filtering XML data
    PHP or PythonFor automating XML feeds
    WordPressTo integrate with plugins or themes
    APIs / REST / JSONTo handle modern integrations
    Hosting & automation toolsTo deploy or sell your XML tools easily

    🚀 Example Plan for You

    Since you already make a WordPress plugin:

    1. Learn advanced XML and XSLT (for powerful feed customization).
    2. Offer a service: “I’ll create XML feeds for your property or job portal.”
    3. Add a paid version of your plugin with feed templates.
    4. Teach others (YouTube or blog) — and monetize traffic.

Powered by