{"id":17,"date":"2026-09-15T12:05:29","date_gmt":"2026-09-15T12:05:29","guid":{"rendered":"https:\/\/microupdate.co.uk\/articles\/?p=17"},"modified":"2026-09-15T12:07:01","modified_gmt":"2026-09-15T12:07:01","slug":"wordfence-aios-a-practical-wordpress-security-setup-without-the-overlap","status":"publish","type":"post","link":"https:\/\/microupdate.co.uk\/articles\/wordpress\/wordfence-aios-a-practical-wordpress-security-setup-without-the-overlap\/","title":{"rendered":"Wordfence + AIOS: A Practical WordPress Security Setup Without the Overlap"},"content":{"rendered":"\n
\n

Wordfence and All In One WP Security can work very well together, but there is a lot of overlap between them.<\/p>\n\n\n\n

Both plugins can protect logins, block malicious requests, restrict access, monitor activity and apply additional WordPress security controls. Simply enabling everything in both plugins is not a good strategy. It can create duplicate protection, conflicting rules, unnecessary processing and make it much harder to work out which plugin has blocked something when a problem occurs.<\/p>\n\n\n\n

A better approach is to give each plugin a clear job.<\/p>\n\n\n\n

Wordfence<\/strong> is the primary security system for the firewall, malware scanning, file comparison, brute-force protection, rate limiting and attack monitoring.<\/p>\n\n\n\n

AIOS<\/strong> complements Wordfence with file and server hardening, permission checks, protection for sensitive files and a number of useful WordPress-specific security controls.<\/p>\n\n\n\n

The tables below show how I would configure the two plugins together. They identify which plugin should handle each security feature, which overlapping settings should normally be disabled, and where the two plugins can safely complement each other.<\/p>\n\n\n\n

The aim is simple: strong everyday WordPress protection without running two competing security systems.<\/strong><\/p>\n\n\n\n

\n
\n

Plugins covered<\/h2>\n\n\n\n
\n
\n

Wordfence Security \u2013 Firewall, Malware Scan, and Login Security<\/h3>\n\n\n\n

Developer:<\/strong> Wordfence<\/p>\n\n\n\n

Availability:<\/strong> Free plugin with paid Premium, Care and Response options.<\/p>\n\n\n\n

Official plugin page:<\/strong> Wordfence on WordPress.org<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

All-In-One Security (AIOS) \u2013 Security and Firewall<\/h3>\n\n\n\n

Developer:<\/strong> Team Updraft<\/p>\n\n\n\n

Availability:<\/strong> Free plugin with Premium upgrade available.<\/p>\n\n\n\n

Official plugin page:<\/strong> AIOS on WordPress.org<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n

This guide covers the current Wordfence and AIOS plugin interfaces. Menu names and option locations can change between releases, so check the official plugin documentation if a setting has moved.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n

Firewall and request protection<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
Web Application Firewall<\/strong><\/td>Firewall Status: Enabled and Protecting<\/strong>. Protection Level: Extended Protection<\/strong>.<\/td>6G \/ 8G firewall rules: OFF<\/strong>. Basic .htaccess<\/code> protection: ON<\/strong>.<\/td>Use Wordfence as the primary WAF. Keep AIOS basic server-level hardening enabled, but avoid overlapping broad firewall rule sets.<\/td><\/tr>
Fake Googlebots<\/strong><\/td>No separate setting required here.<\/td>Block Fake Googlebots: ON<\/strong>.<\/td>Let AIOS handle this specific check.<\/td><\/tr>
Blank User-Agent \/ Referer POST attacks<\/strong><\/td>Equivalent rule: OFF if AIOS handles it<\/strong>.<\/td>Block POST requests with blank User-Agent and Referer: ON, normally<\/strong>.<\/td>Enable this in one plugin only. Use AIOS for this specific rule.<\/td><\/tr>
Rate limiting<\/strong><\/td>Enable Rate Limiting and Blocking: ON<\/strong>.<\/td>Equivalent rate \/ lock controls: OFF<\/strong>.<\/td>Keep request throttling with Wordfence.<\/td><\/tr>
Country blocking<\/strong><\/td>Use Wordfence if Premium.<\/td>OFF if Wordfence handles it<\/strong>.<\/td>Use one country-blocking system only.<\/td><\/tr>
404 attack detection<\/strong><\/td>Rate limiting \/ WAF: Primary defence<\/strong>.<\/td>Smart 404 Blocking: Optional, Premium<\/strong>.<\/td>Wordfence is normally sufficient. Add AIOS Smart 404 Blocking only if there is a clear need.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Malware scanning and file integrity<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
Malware scanning<\/strong><\/td>Standard Scan: ON<\/strong>. Scheduled scans: ON \/ Daily<\/strong>.<\/td>Malware scanner: OFF<\/strong>.<\/td>Use Wordfence as the primary malware scanner.<\/td><\/tr>
WordPress core comparison<\/strong><\/td>Scan core against repository: ON<\/strong>.<\/td>No equivalent required.<\/td>Use Wordfence repository comparison to detect modified core files.<\/td><\/tr>
Plugin comparison<\/strong><\/td>Scan plugins against repository: ON<\/strong>.<\/td>No equivalent required.<\/td>Use Wordfence for repository-backed plugin comparison.<\/td><\/tr>
Theme comparison<\/strong><\/td>Scan themes against repository: ON<\/strong>.<\/td>No equivalent required.<\/td>Use Wordfence for supported repository themes.<\/td><\/tr>
File change detection<\/strong><\/td>File scanning: Primary<\/strong>.<\/td>File Change Detection: Optional<\/strong>.<\/td>Wordfence should remain the main file-integrity system. AIOS can provide an additional notification layer if wanted.<\/td><\/tr>
PHP execution in uploads<\/strong><\/td>Disable Code Execution for Uploads directory: ON<\/strong>.<\/td>No duplicate control required.<\/td>Enable in Wordfence. This is a valuable protection against executable files being run from \/uploads\/<\/code>.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Login and brute-force protection<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
Brute-force protection<\/strong><\/td>Enable brute force protection: ON<\/strong>.<\/td>Login Lockout: OFF<\/strong>.<\/td>Let Wordfence own login throttling and lockouts.<\/td><\/tr>
Failed login threshold<\/strong><\/td>Lock out after login failures: 20<\/strong>.<\/td>OFF<\/strong>.<\/td>Use the Wordfence threshold only.<\/td><\/tr>
Forgot-password threshold<\/strong><\/td>Lock out after forgot-password attempts: 5<\/strong>.<\/td>OFF<\/strong>.<\/td>Keep this under Wordfence.<\/td><\/tr>
Failure counting window<\/strong><\/td>Count failures over: 5 minutes<\/strong>.<\/td>OFF<\/strong>.<\/td>Use the Wordfence setting.<\/td><\/tr>
Lockout duration<\/strong><\/td>1 hour<\/strong>.<\/td>OFF<\/strong>.<\/td>A reasonable starting point for a small business site.<\/td><\/tr>
Invalid usernames<\/strong><\/td>Immediately lock out invalid usernames: ON<\/strong>.<\/td>No duplicate rule required.<\/td>Useful where there are only a few legitimate users.<\/td><\/tr>
Blocked usernames<\/strong><\/td>Immediately block usernames: admin plus known bogus names<\/strong>.<\/td>No duplicate rule required.<\/td>Never add a real username to the blocked list.<\/td><\/tr>
Cookie-based brute-force prevention<\/strong><\/td>Wordfence handles brute-force defence.<\/td>OFF<\/strong>.<\/td>Avoid running a second independent brute-force system.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Passwords, 2FA and login CAPTCHA<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
Breached passwords<\/strong><\/td>Prevent use of breached passwords: ON<\/strong>.<\/td>No duplicate required.<\/td>Use Wordfence.<\/td><\/tr>
Strong passwords<\/strong><\/td>Enforce strong passwords: Admins and publishers<\/strong>.<\/td>No duplicate required.<\/td>Keep password enforcement with Wordfence.<\/td><\/tr>
Two-factor authentication<\/strong><\/td>2FA: ON for administrators<\/strong>.<\/td>Two-factor authentication: OFF<\/strong>.<\/td>Use one 2FA system only.<\/td><\/tr>
Login CAPTCHA<\/strong><\/td>Use Wordfence if required.<\/td>Login CAPTCHA: OFF<\/strong>.<\/td>Avoid two CAPTCHA systems on the same login form.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Username and account protection<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
Login error disclosure<\/strong><\/td>Don’t reveal valid users in login errors: ON<\/strong>.<\/td>No duplicate required.<\/td>Use Wordfence.<\/td><\/tr>
Username discovery<\/strong><\/td>Prevent username discovery through author scans \/ REST \/ oEmbed \/ XML sitemaps: ON<\/strong>.<\/td>Prevent User Enumeration: OFF<\/strong>.<\/td>Keep enumeration protection with Wordfence.<\/td><\/tr>
admin<\/code> username registration<\/strong><\/td>Prevent registration of admin<\/code>: ON<\/strong>.<\/td>Detect admin username: Use as audit only<\/strong>.<\/td>Wordfence blocks future registration. AIOS can be used as a check for an existing account.<\/td><\/tr>
Display name = username<\/strong><\/td>No specific role required.<\/td>Detect identical login\/display names: ON \/ check<\/strong>.<\/td>Use AIOS as an account-hardening audit.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

File and server hardening<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
PHP file editor<\/strong><\/td>No separate control required.<\/td>Disable PHP File Editing: ON<\/strong>.<\/td>Use AIOS to disable theme\/plugin editing from WordPress admin.<\/td><\/tr>
File permissions<\/strong><\/td>No primary role here.<\/td>File Permissions scanner: ON \/ review<\/strong>.<\/td>Use AIOS as an audit tool.<\/td><\/tr>
Sensitive WordPress files<\/strong><\/td>No duplicate required.<\/td>Protect sensitive files: ON<\/strong>.<\/td>Use AIOS.<\/td><\/tr>
Directory browsing<\/strong><\/td>No duplicate required.<\/td>Disable directory listing: ON<\/strong>.<\/td>Use AIOS.<\/td><\/tr>
Server signature<\/strong><\/td>No duplicate required.<\/td>Disable server signature: ON<\/strong>.<\/td>Use AIOS.<\/td><\/tr>
debug.log<\/code> exposure<\/strong><\/td>No duplicate required.<\/td>Block access to debug.log<\/code>: ON<\/strong>.<\/td>Use AIOS.<\/td><\/tr>
WordPress salts<\/strong><\/td>No direct equivalent.<\/td>Salt postfix \/ enhanced salts: ON<\/strong>.<\/td>Use AIOS.<\/td><\/tr>
Database prefix<\/strong><\/td>No action required.<\/td>Change wp_<\/code> database prefix: Do not change purely for security<\/strong>.<\/td>Avoid unnecessary database modification on an established site.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

REST API, XML-RPC and application passwords<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
REST API restrictions<\/strong><\/td>Username enumeration protection: ON<\/strong>.<\/td>Disallow unauthorised REST requests: Usually OFF<\/strong>.<\/td>Protect sensitive user discovery rather than blocking REST generally.<\/td><\/tr>
XML-RPC authentication<\/strong><\/td>XML-RPC authentication protection: ON<\/strong>.<\/td>Disable XML-RPC completely: OFF normally<\/strong>.<\/td>Keep XML-RPC available where required, but protect authentication abuse with Wordfence.<\/td><\/tr>
XML-RPC pingbacks<\/strong><\/td>No separate setting required.<\/td>Disable XML-RPC pingbacks: ON if available and not needed<\/strong>.<\/td>Safer than disabling XML-RPC completely.<\/td><\/tr>
Application passwords<\/strong><\/td>Disable WordPress application passwords: ON unless required<\/strong>.<\/td>No duplicate required.<\/td>Disable unless a genuine integration needs them.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

IP blocking and traffic control<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
IP blocking<\/strong><\/td>Manual IP blocks: Use here<\/strong>.<\/td>IP Blacklist: Normally OFF<\/strong>.<\/td>Keep IP blocking in one place, preferably Wordfence.<\/td><\/tr>
Rate limiting<\/strong><\/td>ON<\/strong>.<\/td>Equivalent controls: OFF<\/strong>.<\/td>Keep traffic throttling with the primary firewall.<\/td><\/tr>
404 probing<\/strong><\/td>WAF \/ Rate Limiting: Primary defence<\/strong>.<\/td>Smart 404 Blocking: Optional, Premium<\/strong>.<\/td>Use Wordfence by default. Add AIOS only if needed.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Logging and monitoring<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
404 logging<\/strong><\/td>Live Traffic: Security Only<\/strong>.<\/td>No duplicate required.<\/td>Avoid logging every visit. Security Only reduces unnecessary database writes.<\/td><\/tr>
Security traffic logging<\/strong><\/td>Live Traffic: Security Only<\/strong>.<\/td>Audit Log: ON<\/strong>.<\/td>These serve different purposes and can coexist. Wordfence records attack activity. AIOS records WordPress security and administrative events.<\/td><\/tr>
File change monitoring<\/strong><\/td>File scanning: Primary<\/strong>.<\/td>File Change Detection: Optional<\/strong>.<\/td>Wordfence remains the main file-integrity tool.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

Additional hardening and optional controls<\/h2>\n\n\n\n
Security feature<\/th>Wordfence<\/th>AIOS<\/th>Recommended approach<\/th><\/tr><\/thead>
Rename login page<\/strong><\/td>Normal login URL is protected by Wordfence.<\/td>Rename Login Page: OFF normally<\/strong>.<\/td>Usually unnecessary and can complicate integrations and password resets.<\/td><\/tr>
Login whitelist<\/strong><\/td>No need in normal use.<\/td>Login whitelist: OFF normally<\/strong>.<\/td>Avoid unless you have a fixed and reliable IP.<\/td><\/tr>
Force logout<\/strong><\/td>No specific requirement.<\/td>Force User Logout: Optional<\/strong>.<\/td>Useful on shared machines or multi-user sites, but not essential for a small admin-only site.<\/td><\/tr>
Manual registration approval<\/strong><\/td>No specific requirement.<\/td>ON only if registration is enabled and approval makes sense<\/strong>.<\/td>Useful where public registration exists.<\/td><\/tr>
Comment spam protection<\/strong><\/td>No primary role here.<\/td>ON if comments are enabled<\/strong>.<\/td>Useful and does not conflict with Wordfence malware protection.<\/td><\/tr>
Image hotlink protection<\/strong><\/td>No primary role here.<\/td>Optional<\/strong>.<\/td>Bandwidth protection rather than a major security control.<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n

Why this configuration works<\/h2>\n\n\n\n

Wordfence and AIOS can work very well together, but only when they are given clearly separated responsibilities.<\/p>\n\n\n\n

Wordfence should handle the main defensive tasks:<\/p>\n\n\n\n

    \n
  • Web Application Firewall<\/li>\n\n\n\n
  • malware scanning<\/li>\n\n\n\n
  • file integrity checking<\/li>\n\n\n\n
  • brute-force protection<\/li>\n\n\n\n
  • rate limiting<\/li>\n\n\n\n
  • login security<\/li>\n\n\n\n
  • attack monitoring<\/li>\n\n\n\n
  • IP blocking<\/li>\n<\/ul>\n\n\n\n

    AIOS then complements Wordfence with additional WordPress and server hardening:<\/p>\n\n\n\n

      \n
    • file permission checks<\/li>\n\n\n\n
    • sensitive file protection<\/li>\n\n\n\n
    • disabling PHP file editing<\/li>\n\n\n\n
    • directory listing protection<\/li>\n\n\n\n
    • debug.log<\/code> protection<\/li>\n\n\n\n
    • selected account security checks<\/li>\n\n\n\n
    • additional WordPress hardening<\/li>\n<\/ul>\n\n\n\n

      The important point is that the two plugins should complement each other rather than compete with each other.<\/p>\n<\/div>\n<\/div>\n\n\n\n

      \n
      \n

      Avoid duplicate protection<\/h2>\n\n\n\n

      Enabling the same protection in both plugins rarely makes the site twice as secure.<\/p>\n\n\n\n

      Instead, it can result in:<\/p>\n\n\n\n

        \n
      • conflicting lockout rules<\/li>\n\n\n\n
      • duplicate CAPTCHA checks<\/li>\n\n\n\n
      • overlapping firewall rules<\/li>\n\n\n\n
      • unnecessary processing<\/li>\n\n\n\n
      • confusing logs<\/li>\n\n\n\n
      • difficulty identifying which plugin blocked a legitimate request<\/li>\n<\/ul>\n\n\n\n

        Where both plugins offer the same feature, choose one plugin to handle it and disable the equivalent control in the other.<\/p>\n\n\n\n

        That also makes future troubleshooting much easier.<\/p>\n<\/div>\n<\/div>\n\n\n\n

        \n
        \n

        Some settings depend on the website<\/h2>\n\n\n\n

        The recommendations in the tables are a strong starting point for a normal WordPress business website, but some sites will need different settings.<\/p>\n\n\n\n

        Take particular care with:<\/p>\n\n\n\n

          \n
        • XML-RPC<\/strong> if the site uses Jetpack, mobile applications or remote publishing<\/li>\n\n\n\n
        • REST API restrictions<\/strong> because many plugins and external services depend on the WordPress REST API<\/li>\n\n\n\n
        • Application passwords<\/strong> if external systems connect to WordPress<\/li>\n\n\n\n
        • Registration controls<\/strong> if visitors are allowed to create accounts<\/li>\n\n\n\n
        • CAPTCHA and login protection<\/strong> if another service already protects the login page<\/li>\n\n\n\n
        • Country blocking<\/strong> where legitimate visitors or administrators may connect from different countries<\/li>\n<\/ul>\n\n\n\n

          Security settings should always reflect how the website is actually being used.<\/p>\n<\/div>\n<\/div>\n\n\n\n

          \n
          \n

          Security plugins are only one part of WordPress security<\/h2>\n\n\n\n

          Wordfence and AIOS provide useful protection, but they cannot compensate for an abandoned plugin, weak passwords or an unmaintained WordPress installation.<\/p>\n\n\n\n

          A secure WordPress site should also have:<\/p>\n\n\n\n

            \n
          • WordPress core kept up to date<\/li>\n\n\n\n
          • plugins and themes updated regularly<\/li>\n\n\n\n
          • unused plugins and themes removed<\/li>\n\n\n\n
          • abandoned software replaced<\/li>\n\n\n\n
          • strong, unique passwords<\/li>\n\n\n\n
          • two-factor authentication for administrator accounts<\/li>\n\n\n\n
          • regular off-site backups<\/li>\n\n\n\n
          • periodic review of administrator accounts<\/li>\n\n\n\n
          • security alerts that are actually monitored<\/li>\n<\/ul>\n\n\n\n

            The objective is not to switch on every available security option.<\/p>\n\n\n\n

            It is to create a simple, understandable security configuration that can be maintained and monitored over time<\/strong>.<\/p>\n<\/div>\n<\/div>\n\n\n\n

            \n
            \n

            Final check<\/h2>\n\n\n\n

            After configuring both plugins, test the website normally.<\/p>\n\n\n\n

            Check:<\/p>\n\n\n\n

              \n
            • administrator login<\/li>\n\n\n\n
            • password reset<\/li>\n\n\n\n
            • contact forms<\/li>\n\n\n\n
            • search<\/li>\n\n\n\n
            • front-end forms<\/li>\n\n\n\n
            • REST-dependent functionality<\/li>\n\n\n\n
            • Jetpack or remote management if used<\/li>\n\n\n\n
            • scheduled jobs<\/li>\n\n\n\n
            • external integrations<\/li>\n<\/ul>\n\n\n\n

              Then review both Wordfence and AIOS logs for unexpected blocks.<\/p>\n\n\n\n

              A security configuration is only useful if it protects the site without preventing legitimate users and services from using it.<\/p>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

              Wordfence and All In One WP Security can work very well together, but there is a lot of overlap between them.<\/p>\n

              Both plugins can protect logins, block malicious requests, restrict access, monitor activity and apply additional WordPress security controls. Simply enabling everything in both plugins is not a good strategy. It can create duplicate protection, conflicting rules, unnecessary processing and make it much harder to work out which plugin has blocked something when a problem occurs.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","_seopress_news_disabled":"","_seopress_video_disabled":"","_seopress_video":[],"_seopress_pro_schemas_manual":[],"_seopress_pro_rich_snippets_disable_all":"","_seopress_pro_rich_snippets_disable":[],"_seopress_pro_schemas":[],"footnotes":""},"categories":[7,6],"tags":[],"class_list":["post-17","post","type-post","status-publish","format-standard","hentry","category-malware","category-wordpress"],"_links":{"self":[{"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/posts\/17","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/comments?post=17"}],"version-history":[{"count":6,"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/posts\/17\/revisions"}],"predecessor-version":[{"id":41,"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/posts\/17\/revisions\/41"}],"wp:attachment":[{"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/media?parent=17"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/categories?post=17"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microupdate.co.uk\/articles\/wp-json\/wp\/v2\/tags?post=17"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}