Summary: - I reran the WordPress inspection with working `wp-cli`, confirmed the live front page/blog/menu/footer state, then fixed the review issues directly in content. - Public schedule/address/phone references were tightened around the church’s current public contact details: Sunday classes are now `8:45 a.m.`, worship is `10:00 a.m.`, Wednesday ministries now say they begin at `6:30 p.m.`, and the broader unsupported location/community phrasing was reduced to safer wording. - The required external links were reduced to 3 total and redistributed contextually across page bodies instead of being clustered in one `Resources` subsection. WP changes: - Updated `Home`, `Ministries`, `Kids`, `Youth`, `Events Calendar`, `News`, `Church Map`, and `Resources`. - Replaced the old `9:00 a.m.` / `6:30 to 8:00 p.m.` copy with verified-or-safer wording across the affected pages. - Removed the old single five-link external resource list from `Resources`. - Kept only these contextual link placements: - `https://flatlogic.com/services/custom-web-development-services?utm_source=ridgecrestchurch.com` with anchor `custom web development services` on `Ministries` - `https://flatlogic.com/generator?utm_source=ridgecrestchurch.com` with anchor `web app generator` on `Events Calendar` - `https://appwizzy.com/` with anchor `vibe coding tool` on `Resources` - Kept the active `church` theme, primary navigation, static front page, blog index, and footer legal/contact links intact. - Tightened the public tagline to `A welcoming family church in Blanchard, Oklahoma`. - Remaining uncertainty: the public email is still the task-default `admin@ridgecrestchurch.com`; phone/address/times were externally corroborated, but I did not find an independently published replacement mailbox during this pass. Manual checks: - `wp option get show_on_front` = `page`, `page_on_front` = `13`, `page_for_posts` = `23`. - `wp menu list` and `wp menu item list primary-navigation` confirmed the primary menu with all main pages plus `Blog`. - `wp post url` confirmed the expected URLs for Home, Events Calendar, Resources, Contacts, Blog, and all legal pages. - `curl -I -L` returned `HTTP/2 200` for `/`, `/blog/`, `/events-calendar/`, `/resources/`, `/contacts/`, `/church-map/`, `/privacy-policy/`, `/terms-of-use/`, and `/cookie-policy/`. - Rendered HTML checks confirmed the footer still contains contact/legal links, the header shows the Ridgecrest identity/tagline, and the three required external links are now spread across separate body sections. ```text WP_PAGE_BATCH_STATUS: completed WP_PAGES_CREATED_OR_UPDATED: Home=13=https://ridgecrestchurch.com/; About Us=14=https://ridgecrestchurch.com/about-us/; Ministries=15=https://ridgecrestchurch.com/ministries/; Kids=16=https://ridgecrestchurch.com/kids/; Youth=17=https://ridgecrestchurch.com/youth/; Events Calendar=18=https://ridgecrestchurch.com/events-calendar/; News=19=https://ridgecrestchurch.com/news/; Contacts=20=https://ridgecrestchurch.com/contacts/; Church Map=21=https://ridgecrestchurch.com/church-map/; Resources=22=https://ridgecrestchurch.com/resources/; Blog=23=https://ridgecrestchurch.com/blog/; Privacy Policy=24=https://ridgecrestchurch.com/privacy-policy/; Terms of Use=25=https://ridgecrestchurch.com/terms-of-use/; Cookie Policy=26=https://ridgecrestchurch.com/cookie-policy/ THEME_STATUS: church; kept; suitable free church theme already active and working HEADER_IDENTITY_STATUS: configured; Ridgecrest Baptist Church logo with tagline "A welcoming family church in Blanchard, Oklahoma" LEGAL_PAGES_STATUS: created FOOTER_STATUS: email-and-utility-links-present FRONT_PAGE_SET: yes BLOG_INDEX_STATUS: existing; https://ridgecrestchurch.com/blog/ with page_for_posts=23 MENU_UPDATED: yes LEGACY_PATH_STATUS: restored BACKLINK_PAGE_TARGETS_STATUS: restored POST_TARGETS_RESERVED: none LINK_TARGETS_USED: https://flatlogic.com/services/custom-web-development-services?utm_source=ridgecrestchurch.com, https://flatlogic.com/generator?utm_source=ridgecrestchurch.com, https://appwizzy.com/ VERIFICATION: wp-cli confirmed theme/front-page/blog/menu/page state; curl returned HTTP 200 for core pages; rendered HTML shows corrected schedule wording, footer links, and redistributed external placements ```