Getting the Scott Stamp Catalogue Spain Data onto Your WordPress Site

The Scott Stamp Catalogue Spain is one of the standard reference works for anyone dealing with Spanish philately. The digital version covers stamps from the 1850s onward, with catalog numbers, Michel cross-references, and current pricing tiers. Most people end up on WordPress because they want a searchable, publicly accessible database rather than a static PDF they can't really work with. I spent about three weeks building exactly this for a collector's site, and here's what actually worked. You're not downloading a pre-made WordPress theme called "Scott Stamp Catalogue Spain." What you're really looking for is the data format, a way to import it, and a plugin structure that can display it cleanly. Let me walk through the full process. First, you need the catalogue data itself. Scott Publishing sells digital versions of their catalogues, and the Spain volume is available as a downloadable file, typically in XML or CSV format depending on your subscription tier. Make sure you have the appropriate license before doing anything else. This isn't free data. Using unauthorized copies will get your site taken down quickly.

I found the XML format to be the most reliable for import purposes. Scott's XML structure nests each stamp entry with attributes for issue date, catalog number, denomination, and Scott number. A few fields are inconsistently populated across different regions of Spain and the former colonies, so don't expect perfect data quality right out of the box.

Setting Up the WordPress Structure

Once you have the data, you need a place to put it. A custom post type called something like stamp_catalogue works better than using regular posts. The problem with using standard WordPress posts is that taxonomy gets messy fast. You end up mixing editorial content with structured data, and the two don't play nicely together.

I created the following custom fields using Advanced Custom Fields or a similar plugin:

Get the Full Details

PPT - download Scott Standard Postage Stamp Catalogue 2023: Countries G-I (3) (Scott C ...
PPT - download Scott Standard Postage Stamp Catalogue 2023: Countries G-I (3) (Scott C ...
  • Scott Catalog Number (text field)
  • Issue Date (date field)
  • Denomination (text field)
  • Michel Reference (text field)
  • Condition Pricing - Unused (textarea with structured notes)
  • Condition Pricing - Used (textarea with structured notes)
  • Stamp Category (taxonomy: definitive, commemorative, airmail, etc.)

After setting up the fields, I wrote a simple PHP importer script that reads the XML and creates posts programmatically. This is important because trying to copy-paste thousands of entries manually is not realistic. The script ran for about forty minutes on a standard hosting environment and created roughly 3,200 entries for the Spain volume alone.

Importing and Mapping the Data

Here's where things get tricky. Scott's numbering system changed significantly in the modern era. The older single-number system gives way to a more complex variant numbering scheme that includes letter suffixes and numeric sub-entries. Your importer needs to handle both formats, or you'll end up with duplicate entries or missing records.

I encountered a specific problem during the import where certain Spanish colonial issues from the late 1800s had Scott numbers that didn't map cleanly to a single post. The XML would list something like "Spain 45a" and "Spain 45b" as separate entries but with overlapping metadata. The result was posts that referenced the same physical stamp but appeared as completely unrelated items in the archive. The workaround was to add a pre-processing step to the import script. I grouped entries by their base Scott number before creating posts, then used a repeater field for variants instead of separate posts. This meant a single post could represent a main stamp and all its legitimate variants. The tradeoff is that filtering by exact Scott number becomes slightly more complex on the frontend, but the data integrity is much better.

Display and Search Considerations

A catalog of over three thousand entries is useless if you can't search it efficiently. WordPress's default search won't cut it. I ended up using a combination of FacetWP and a custom search form that queries the metadata fields directly. This lets users filter by decade, issuing authority, denomination range, and catalog status. One counter-intuitive thing I learned: putting the Scott number as the post title actually hurts searchability. Google and WordPress both treat post titles as primary identifiers, and when your titles look like "1850 - 5c blue - Scott #12a," the search algorithms get confused about what the user actually wants. I moved the Scott number into a dedicated metadata field and used cleaner titles like "Spain 1850 First Issue 5c Blue." The search results became significantly more accurate after that change.

Performance and Hosting Reality

PPT - download Scott Standard Postage Stamp Catalogue 2023: Countries G-I (3) (Scott C ...
PPT - download Scott Standard Postage Stamp Catalogue 2023: Countries G-I (3) (Scott C ...

Don't skimp on hosting if you're running a large catalogue on WordPress. I initially put this on a shared hosting plan and the database queries during peak traffic caused serious slowdowns. Moving to a managed WordPress host with a dedicated database connection resolved the issue. Page load times for catalogue listings went from around four seconds down to under one second. If you're considering a different approach entirely, there are dedicated stamp catalog plugins available, but they tend to be generic and don't handle the Scott numbering scheme well. The custom implementation approach takes more upfront work but gives you full control over the data structure and display logic. The total time investment for a clean implementation like this is somewhere between fifteen and twenty hours if you're comfortable with PHP and WordPress development. A less experienced person should budget closer to forty hours due to troubleshooting the import script and debugging taxonomy conflicts. Factor in additional time if you plan to add pricing data updates, which is something most people underestimate.