Search is no longer just about ranking pages. These FAQs cover SEO, AI, AEO, schema, answer readiness, and the practical choices that help your content become easier for people and search systems to understand.
Still can’t find what you are looking for? Try
ChatGPT.
Will redesigning my website hurt SEO?
Redesigning a website can hurt SEO when important pages are removed, URLs change without redirects, content gets weaker, internal links disappear, or technical settings are misconfigured. Those risks are common when SEO is treated as a launch cleanup task.
A redesign can also improve SEO when search visibility is part of the plan from the beginning. Better structure, clearer content, stronger internal linking, improved performance, and cleaner technical implementation can all help.
The difference is planning. Protect the pages and signals that already have value, then use the rebuild to improve what was not working.
AEO, or answer engine optimization, is the practice of structuring content so answer engines can understand the question, identify the useful answer, and connect that answer to credible supporting context. It builds on SEO foundations like crawlability, helpful content, internal links, metadata, and structured data, but it puts extra emphasis on clear answers, trust signals, and topic depth.
Should I keep the same URLs during a website rebuild?
Keep the same URLs during a website rebuild whenever the page is still relevant and has search value. Keeping a stable URL reduces migration risk because search engines and users do not need to rediscover where the content moved.
Changing URLs is sometimes necessary, especially when the old structure is confusing or the content strategy has changed. When a URL changes, the old page should be mapped to the most relevant new page with a 301 redirect.
The decision should be made page by page. Preserve what has value, improve what needs work, and avoid changing URLs casually.
The primary browsable FAQ experience is the FAQ hub at smithworks.marketing/faqs. Content is stored in HubDB and rendered by SW FAQs Advanced HubDB on hub index and category pages. Visitors can search, filter by topic tags, and open paginated category lists.
For humans: Start at the FAQ hub when choosing modules, understanding HubDB setup, or reading upgrade-related behavior.
For AI agents: Treat the hub as an additional grounding source alongside SW Module Documentation (exact fields) and docs.smithworks.marketing (dated changes). Do not invent module names or field paths when the hub or AI documentation does not support an answer.
The legacy page /sw-module-faqs is being superseded by the HubDB-backed hub; prefer /faqs for current content.
Do I need redirects when rebuilding my website?
Yes. If important URLs change during a website rebuild, redirects are necessary to preserve as much search equity and user continuity as possible.
A 301 redirect tells search engines and visitors that the old URL has moved permanently to a new location. Without that step, valuable pages can disappear, backlinks can break, and users may hit dead ends instead of the content they expected.
Redirect planning should happen before launch, not after. The best approach is to map old URLs to the most relevant new URLs, test them carefully, and monitor performance after launch.
The SW Module Documentation page is written for AI agents (ChatGPT, Claude, Cursor, etc.) and technical implementers. It provides exact module names, Content vs Style tab paths, group names, field labels, and rules such as “do not invent fields.”
Use three layers:
FAQ hub — human-friendly and AI-grounding Q&A (HubDB, hub setup, when to use which module).
AI agents should read the FAQ hub for context, then open the AI documentation for the specific module being edited.
What pages should I protect during a rebuild?
Protect pages that already have business or search value during a rebuild. That includes pages with organic traffic, impressions, rankings, backlinks, conversions, assisted conversions, or important service information.
A page does not have to be perfect to be worth protecting. It may need better copy, clearer calls-to-action, stronger internal links, or improved structure, but deleting it casually can create avoidable SEO and user-experience problems.
Before launch, review performance data, Search Console data, analytics, backlinks, and sales usefulness so important pages are either preserved, improved, redirected, or intentionally retired.
Start monitoring SEO immediately after launch. Some issues are visible right away, such as broken redirects, noindex mistakes, crawl errors, missing pages, or analytics problems.
Other changes may take longer to appear because search engines need time to recrawl and process the new site. During the first several weeks, watch Search Console, analytics, ranking changes, impressions, clicks, indexing status, and conversion behavior.
Post-launch monitoring is not just about finding problems. It also helps confirm whether the rebuild is helping the site become clearer, more discoverable, and more useful.
What should I do if an SW module is not documented?
If an SW module is not documented, the safest answer is to say that it is not documented and avoid guessing. The AI documentation specifically warns agents not to invent module names, field paths, or behaviors.
Use the documented modules as the source of truth. If the user needs a module added to their portal, custom module work, or help with an undocumented module, they should use the Smithworks support or module access path.
How is AEO different from SEO?
SEO and AEO are connected. SEO focuses on helping search engines crawl, understand, rank, and display your content. AEO focuses on making the answer itself easier to extract, verify, and cite in AI-influenced search experiences and other answer-style interfaces. The same SEO fundamentals still matter, but AEO adds pressure to make content clearer, better sourced, and more connected to surrounding expertise.
