{ "schemaVersion": "1.0", "kind": "entity-answers", "id": "https://thatstupidcomputer.com/knowledge/answers.json", "organizationId": "https://thatdeveloperguy.com/#organization", "primaryEntityId": "https://thatdeveloperguy.com/#brand-thatstupidcomputer", "masterManifest": "https://feedthejoe.com/organization/knowledge/index.json", "siteManifest": "https://thatstupidcomputer.com/knowledge/index.json", "reviewed": "2026-10-06", "answers": [ { "id": "https://thatstupidcomputer.com/knowledge/answers.json#organization-provider", "question": "Who provides That Stupid Computer’s website services?", "answer": "ThatStupidComputer is a brand of ThatDeveloperGuy, the organization that provides our website services. This website is published by ThatDeveloperGuy.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer", "https://thatdeveloperguy.com/#organization" ], "sources": [ "https://thatstupidcomputer.com/about/#our-organization", "https://thatdeveloperguy.com/brands/that-stupid-computer", "https://feedthejoe.com/organization/knowledge/" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#project-cost", "question": "What does it cost?", "answer": "There is no fixed price published here because a repair, a small new site and an application have different scopes. Share the goal and any budget or timing constraints so the conversation can begin with a realistic fit. Work, cost and responsibilities need to be agreed before a project starts.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/#project-cost" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#website-design-scope", "question": "What goes into a business website?", "answer": "The scope starts with who you serve, what you offer and what a customer needs to know before contacting you. Those answers determine the pages, content and features that belong in the build.\n\nPage structure and a clear path to an inquiry.\n\nContent planning around real services and customer questions.\n\nVisual design and interactions that support the message.\n\nResponsive development, practical checks and a considered handoff.", "about": [ "https://thatstupidcomputer.com/services/website-design/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-design/#website-design-scope" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#website-content-preparation", "question": "Do I need all my content and branding ready?", "answer": "No. An outline of your business, your services and the purpose of the site is enough for the first conversation. Bring existing branding, draft text, photographs you can use and examples you like if you have them. Scoping should establish what is already available, who will prepare the remaining content and when it is needed.", "about": [ "https://thatstupidcomputer.com/services/website-design/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-design/#website-content-preparation" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#website-deliverables", "question": "What should a website project include?", "answer": "Agree on a page inventory, the actions customers need to complete and the material each page requires. The proposal should identify the design and development deliverables, review rounds, account access, content responsibilities and launch checks.\n\nList required features, such as a project inquiry, a gallery or a booking integration.\n\nDefine which devices and browsers will be checked, and how content works when motion or scripts are unavailable.\n\nIdentify who controls the domain, hosting, email and third-party accounts.\n\nRecord what will be handed over and which updates need an ongoing care agreement.", "about": [ "https://thatstupidcomputer.com/services/website-design/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-design/#website-deliverables" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#redesign-existing-urls", "question": "What happens to existing links when a website is redesigned?", "answer": "Plan the existing addresses before changing them. Useful pages can keep their URLs even when their design changes. When a page moves, map its old address to the closest relevant replacement and test the permanent redirect. Sending every old page to the homepage can leave visitors without the information they followed a link to find.\n\nInventory the important pages and downloads, including destinations in search reports or links from other websites.\n\nUpdate internal links, canonical addresses and the sitemap to the chosen URLs.\n\nKeep a real missing-page response for removed content that has no relevant replacement.\n\nCheck the old and new public addresses after launch and monitor search reports; a planned migration still does not guarantee unchanged rankings.", "about": [ "https://thatstupidcomputer.com/services/website-design/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-design/#redesign-existing-urls", "https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#repair-access-and-backups", "question": "What access is needed to diagnose a website problem?", "answer": "The first checks can often use the public page and your steps to reproduce the failure. A code, hosting or email problem may then require access to the system involved. Agree on the affected site and permitted changes before granting access.\n\nUse a separate, limited account where the platform supports it.\n\nConfirm the current backup and a way to restore the previous version before changing production.\n\nShare credentials through an agreed secure method, outside the project inquiry form.\n\nKeep customer records and live email out of test data unless a specific test has been authorized.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#repair-access-and-backups" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#repair-acceptance", "question": "How do you check that a repair worked?", "answer": "Repeat the original failure with the same steps, then check the related customer tasks it could affect. For a form, distinguish validation, sending-service acceptance and actual inbox receipt. For navigation, check direct page links and the Back button as well as the route that first failed.\n\nRetain a clear description of the fault and the change that addressed it.\n\nRun the agreed checks against the deployed site, where hosting and cache behavior can differ.\n\nRecord any devices, integrations or failure cases that remain untested.\n\nKeep the previous working release available until the agreed checks pass.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#repair-acceptance" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#repair-or-rebuild", "question": "Can you repair my website without rebuilding it?", "answer": "Often, a specific failure can be repaired without replacing the whole website. The decision starts with whether the current platform can still support your content, security needs and customer journey—not whether someone prefers a different framework.\n\nRepair when the cause is isolated and the existing site can be maintained safely.\n\nConsider a rebuild when essential changes keep colliding with unsupported software, fragile integrations or a structure that no longer fits the business.\n\nCompare the actual work, disruption, ownership and ongoing maintenance before choosing. A new design alone does not fix a broken inquiry pipeline.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#repair-or-rebuild" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#public-website-testing", "question": "Why does it work for me but not for my customers?", "answer": "Your device may be using a private connection, an old cached response or a different network route. A page loading on the hosting server proves something different from that same page loading for a visitor.\n\nRepeat the problem using the exact public address, outside the private connection.\n\nCheck the secure connection, redirects and the actual response from that address.\n\nRepeat the customer’s task on the affected browser and device. Record the failing step, not just a screenshot of the homepage.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#public-website-testing" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#form-delivery", "question": "The form says sent. Did the message arrive?", "answer": "Not necessarily. A browser confirmation, acceptance by a mail server and arrival in your inbox are separate events. A useful repair follows one authorized test message through those stages and checks the destination, including filtering, instead of changing the button text to say success.", "about": [ "https://thatstupidcomputer.com/services/website-rescue/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-rescue/#form-delivery" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#search-visibility-scope", "question": "What does the work actually include?", "answer": "The scope starts with your website and the questions your customers need answered. A useful improvement should leave you with something you can inspect, not an unexplained AI score.\n\nA page-by-page check of public access, redirects, canonical addresses and discovery rules.\n\nClear answer destinations for real services and customer decisions, with gaps called out.\n\nConsistent public business facts, visible content and appropriate structured data.\n\nSeparate provider checks for search discovery, model training and user-requested retrieval.\n\nA measured baseline and a record of the changes, tests and results that can actually be observed.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#search-visibility-scope" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#website-not-in-search", "question": "My website is online. Why is it not showing up in search?", "answer": "Being online is the starting point. Check whether the important pages can be crawled, are indexed and explain the service a customer is searching for. A homepage that appears for your business name may still leave a specific service poorly explained. The next step depends on the gap: repair an access problem, improve an existing page or clarify the route to it.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#website-not-in-search" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#bing-backlinks", "question": "Does Bing register every backlink?", "answer": "No. Bing’s backlink report is a representative sample of detected links, not a complete inventory. A business identity reference, a canonical relationship and a clickable link from another page are different things. An empty detail list does not prove that no links exist.\n\nCompare the exact referring page and destination, not just the business name.\n\nKeep your own published relationships separate from links observed by Bing.\n\nTreat sitemap submissions and IndexNow notifications as discovery messages, not backlink registration or ranking credit.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#bing-backlinks", "https://www.bing.com/webmasters/help/backlinks-c3a334e8" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#useful-ai-answers", "question": "What makes a page useful in an AI answer?", "answer": "A clear answer to a real question, enough context to interpret it correctly and evidence for the claims. A repair page should explain when repair makes sense, what needs testing and what a customer should provide. A comparison should make the tradeoffs understandable. The format follows the question.\n\nState the answer clearly, then explain the conditions and limitations.\n\nSupport factual claims with relevant sources or genuine, approved work examples.\n\nKeep the same facts available to people and automated readers.\n\nGive the reader a useful next step; do not create a page for every keyword variation.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#useful-ai-answers" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#distinct-service-pages", "question": "Do I need a page for every town or keyword?", "answer": "A separate page should help a customer make a different decision or understand a genuinely different service. Changing a town name or repeating the same offer with another keyword does not create a useful destination. Google identifies substantially similar pages that funnel people elsewhere as a form of doorway abuse.\n\nStart with the services you actually provide and the questions each page needs to answer.\n\nPublish location details only when they describe a real service area or location and add useful, supported information.\n\nKeep one clear destination when several search phrases describe the same need.\n\nUse original examples and practical explanations where available; do not invent local offices, reviews or results to fill a page.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#distinct-service-pages", "https://developers.google.com/search/docs/essentials/spam-policies#doorway-abuse" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#provider-specific-support", "question": "Does every AI model need the same integration?", "answer": "No. Separate provider modules should handle the controls, API requests, response formats and measurement that each product actually supports. A shared registry can connect those modules while the public answers and approved business facts stay consistent. That is different from maintaining competing copies of the business for each model.\n\nWrite in the language your customers use; these pages use English.\n\nUse the provider’s documented data format for an integration, rather than inventing a special writing language.\n\nKeep useful answers visible on their canonical pages. Google explicitly does not require special AI files or special schema.\n\nRecord the exact model and interface used in a test. A developer API result is not automatically a result from its consumer chat product.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#provider-specific-support", "https://developers.google.com/search/docs/fundamentals/ai-optimization-guide" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#measuring-visibility", "question": "How do we measure whether it helped?", "answer": "Keep access, visibility and visits separate. A verified crawler request shows retrieval activity. An indexed page shows index inclusion. A captured AI answer can show a citation. Website analytics can show an attributable visit. None of those observations alone proves an inquiry or a sale.\n\nCompare the same pages and reporting windows, with releases noted.\n\nRecord the exact AI product, question, date and cited page when sampling answers.\n\nKeep a completed answer without a citation separate from an unavailable test.\n\nReport the limits alongside the results. Rankings and AI source selection remain the provider’s decision.", "about": [ "https://thatstupidcomputer.com/services/search-visibility/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/search-visibility/#measuring-visibility" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#maintenance-and-hosting", "question": "Is website maintenance the same as hosting?", "answer": "Hosting provides the system that serves your website. Maintenance is the work of keeping its content, software and important features in order. Domain registration and third-party subscriptions are separate responsibilities too. A care agreement should identify which services are covered, who controls each account and who can act when something fails.", "about": [ "https://thatstupidcomputer.com/services/website-care/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-care/#maintenance-and-hosting" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#backup-and-recovery", "question": "Does having a backup mean the website can be restored?", "answer": "A saved copy is only part of recovery. The plan also needs the right files, account access and a tested way to restore them. For a website with a database or uploaded media, copying the application code alone may leave out the information the site needs.\n\nAgree what is backed up, where it is kept, how long copies are retained and who can restore them.\n\nIdentify dependencies outside the website, such as domain settings, email and third-party integrations.\n\nTest recovery in a suitable separate environment before relying on it during an outage.\n\nRecord the last recovery check and any limits on how much recent information can be recovered. Recovery timing and coverage belong in the agreed plan.", "about": [ "https://thatstupidcomputer.com/services/website-care/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-care/#backup-and-recovery" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#maintenance-evidence", "question": "What should a website maintenance report tell me?", "answer": "It should explain what changed, what was checked and what still needs a decision. A list of software updates is useful, but it does not show whether a customer can read the service pages, navigate on a phone or submit an inquiry.\n\nName the affected pages or systems and the reason for each change.\n\nRecord the customer tasks checked after the update and the result of those checks.\n\nSeparate monitoring alerts, sending-service acceptance and confirmed message receipt.\n\nFlag failed checks, untested integrations and upcoming renewals with a responsible account owner.\n\nKeep access details and private customer information out of the report.", "about": [ "https://thatstupidcomputer.com/services/website-care/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-care/#maintenance-evidence" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#maintenance-incident-response", "question": "What happens if something breaks?", "answer": "Agree on the contact route, response expectations and work covered by the care plan before a problem occurs. A new feature or a larger repair may need a separate scope. Make backup and recovery responsibilities explicit so the plan covers more than routine content changes.", "about": [ "https://thatstupidcomputer.com/services/website-care/#service", "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/services/website-care/#maintenance-incident-response" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#inspect-the-working-example", "question": "What can you inspect in this example?", "answer": "This is a first-party demonstration: the work being described is the website you are using. The public pages deliver their headings, service explanations and ordinary links in the initial page. The illustrated room and character controls add another way to explore that content.\n\nOpen a service directly, then use its breadcrumbs and related links to move through the site.\n\nTry the motion control or your device’s reduced-motion setting while reading the same information.\n\nFollow the organization link to see who provides the services and how the related websites connect.\n\nReview the project brief and privacy explanation before deciding what information to send.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/work/#inspect-the-working-example" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#work-example-scope", "question": "What does this example demonstrate?", "answer": "It demonstrates the site’s visual approach, navigation, character interaction and service-to-inquiry design. It is an owned project rather than a client testimonial. No client revenue increase, search ranking or conversion result is attributed to this example. The right level of motion and detail for your project should follow your audience and the task they need to complete.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/work/#work-example-scope" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#project-acceptance", "question": "What should be checked before a website goes live?", "answer": "Start with the customer tasks agreed in scope. Verify the important pages and links, readable layouts, keyboard access, contact route and error messages. Review public names, services, contact details and search metadata against the approved content.\n\nCheck the real deployment address and redirects, including what happens at a missing page.\n\nConfirm that private records and access credentials are outside public files.\n\nVerify the agreed contact or transaction path using an authorized test.\n\nName the release, remaining limitations, responsible account owners and recovery procedure.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/process/#project-acceptance" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#project-timing", "question": "How long will the project take?", "answer": "Timing depends on the scope, content readiness, integrations and review availability. A targeted repair and a new website need different plans. Agree on milestones after those dependencies are understood, and make the effect of delayed content or new requirements explicit. No fixed delivery time is promised before that review.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/process/#project-timing" ], "evidenceClass": "owner-published" }, { "id": "https://thatstupidcomputer.com/knowledge/answers.json#inquiry-next-step", "question": "What happens after you send?", "answer": "The form sends the project brief by email when the inquiry service is available. Its confirmation means the mail service accepted the request for sending; it does not confirm arrival in the inbox or that a person has read it. A project or appointment is agreed through a follow-up conversation.", "about": [ "https://thatdeveloperguy.com/#brand-thatstupidcomputer" ], "sources": [ "https://thatstupidcomputer.com/contact/#inquiry-next-step" ], "evidenceClass": "owner-published" } ] }