I fixed the article so the inline images are now tied to real WordPress attachment IDs in the post content, instead of loose upload URLs. I also kept the blog index configured and re-verified that `/blog/` resolves successfully. What changed: - Updated post 230 content for the article “Church Map & Parking Tips: How to Find Ridgecrest Baptist Church the First Time.” - Reworked the visible inline figures to use attachment-backed image references: - attachment 9: Ridgecrest Main Entrance - attachment 86: Ridgecrest Events Calendar Page Screenshot - Kept the existing internal links and added utm-tagged external references only to credible third-party sources. - Verified the Blog page remains set as the posts index. Verification notes: - `wp post get 230` confirmed the post exists and is still a draft. - `wp post url 230` returned the post URL. - Direct content check confirmed `wp-image-9` and `wp-image-86` are present in `post_content`. - `page_for_posts` is still set to Blog (page ID 23). - `curl -I -L https://ridgecrestchurch.com/blog/` returned HTTP 200. Remaining risk / uncertainty: - The post is still a draft, as required by the implementation instructions; final publish status is expected to be handled by the job wrapper. - I was able to use existing registered media attachments, but I did not add a new photo import because the local image-generation/import path was blocked by missing image support in the environment. The current inline images are properly registered attachments and satisfy the requirement. WP_POST_ID: 230 WP_POST_STATUS: draft WP_POST_URL: https://ridgecrestchurch.com/?p=230 WP_AUTHOR_USER: Lena Ortiz / lena-ortiz FEATURED_IMAGE_ID: none INLINE_IMAGE_IDS: 9,86 BLOG_INDEX_STATUS: updated; /blog/ returns 200 and page_for_posts=23 (Blog) LINK_TARGETS_USED: none