Budget: 5000 UAH Deadline: 30 days
Hello!
Attempting to stop the server from falling due to 700 thousand spam pages by blocking access for Google (error 403) is a treatment of symptoms that has completely paralyzed your business. The problem is not in the console settings, but in the fact that the virus physically remains in the database or your custom scripts, which is why Google Ads rightly rejects the closed and infected resource.
Avoiding masking the problem: Closing indexing through Google Search Console does not remove the virus, it only "closes the eyes" of the search engine. To restore advertising, it is necessary to thoroughly clean the malicious code from the server and set a mass return status of 410 (Gone) for all generated junk so that the Ads algorithms can see a safe site again.
The danger of "blind" migration: Changing the WordPress template will not solve the problem if the virus resides in the database or hides in the vulnerabilities of your custom PHP calculators. Simply transferring this code to a new theme is a guaranteed transfer of the backdoor to a fresh architecture and re-infection.
Technical synchronization instead of chaos: As long as the server returns a 403 error (access denied) to Google scanners, any attempts to launch paid traffic will be blocked by automatic security filters. The priority is to restore the clean architecture of server responses, not to manipulate the visuals.
What is the point of wasting time switching templates and trying to bypass Ads blocking if the root cause (malicious code in the database or calculators) continues to live on your server, burning your potential revenue from halted advertising every day?
Sincerely, Arseniy.